[DOC-13899]: Create a release note for Couchbase Server 8.0.1

[RayOffiah]

Created: 04/03/2026

Preview URL:
https://preview.docs-test.couchbase.com/docs-server-DOC-13899-Create-a-release-note-for-Couchbase-Server-8.0.1/server/current/release-notes/relnotes.html

You will need the Docs Team credentials on Confluence.

[Copilot]

Pull request overview

Adds the Couchbase Server 8.0.1 release-notes content to the release notes section of the documentation, so it renders on the main relnotes.adoc page.

Changes:

• Introduces a new partial for 8.0.1 fixes and improvements with service-specific “Fixed Issues” entries.
• Updates the release notes page to include the new 8.0.1 partial ahead of the existing 8.0.0 content.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 9 comments.

File	Description
modules/release-notes/partials/docs-server-8.0.1-fixes-and-improvements.adoc	New 8.0.1 “Fixed Issues” release-note content organized by service.
modules/release-notes/pages/relnotes.adoc	Includes the new 8.0.1 partial in the rendered release notes page.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The MB-70112 paragraph has a double space ("made with the auto_execute") and the phrase "error out with error" is redundant. Tightening the wording will make the release note easier to scan.

Suggested change

	When a prepared request is made with the `auto_execute` request parameter set as `true`,
	the request would incorrectly error out with error: `Unrecognizable prepared statement - cause: JSON unmarshalling error: auto_execute did not produce a prepared statement`
	When a prepared request is made with the `auto_execute` request parameter set as `true`,
	the request would incorrectly return the following error: `Unrecognizable prepared statement - cause: JSON unmarshalling error: auto_execute did not produce a prepared statement`

[Copilot]

This entry is missing ending punctuation. Please add a period (and consider rephrasing "Fixes a bug" to a past-tense or neutral release-notes style if that’s the pattern elsewhere in this document).

Suggested change

	Fixes a bug where buckets with cross-cluster versioning enabled (link:https://docs.couchbase.com/server/current/learn/clusters-and-availability/xdcr-enable-crossclusterversioning.html[XDCR enable cross-cluster versioning]) would cause a merge to fail
	Addressed a bug where buckets with cross-cluster versioning enabled (link:https://docs.couchbase.com/server/current/learn/clusters-and-availability/xdcr-enable-crossclusterversioning.html[XDCR enable cross-cluster versioning]) would cause a merge to fail.

[Copilot]

The MB-70441 description uses the term "peer certification", which is ambiguous and may be incorrect in a TLS context. Consider rephrasing to explicitly describe the behavior (for example, peer certificate verification against the OS trust store) so readers understand what changed.

Suggested change

	The upgrade to Erlang version 26 introduced a change in behavior which requires peer certification when TLS is being used for Alert emails.
	The peer certification introduced with the changes for this ticket uses the trusted CA certificates provided by the operating system.
	The upgrade to Erlang version 26 introduced a change in behavior which requires verification of the peer's TLS certificate when TLS is being used for Alert emails.
	This peer certificate verification uses the trusted CA certificates provided by the operating system (the OS trust store).

[Copilot]

MB-68969 appears here under Search Service with the same text already listed under Query Service. Please confirm whether this issue actually affects Search Service; if not, remove it or replace it with the correct Search Service fixed-issue ID and description.

Suggested change

	*https://jira.issues.couchbase.com/browse/MB-68969/[MB-68969]*::
	* With multi-collection indexes that contained fields with `include in _all` setting enabled - there was a possibility for false positives to show up for field agnostic (composite field) queries.
	This has been addressed by denying the sargability for such indexes.
	* Addressed an issue where fields not belonging to a particular keyspace were being included in multi-collection indexes.
	* Addressed a bug that could influence composite field (`_all`) availability based on the order in which fields were processed.
	No Search Service-specific fixes are listed for this release.

[Copilot]

Please remove the in-file note "generated by gemini:gemini-2.5-flash". This metadata is not user-facing documentation and will ship in published release notes if left in place.

Suggested change

// generated by gemini:gemini-2.5-flash

[Copilot]

This sentence has a couple of readability issues: missing comma after "In 8.0.0", "7.6 and below" is awkward phrasing (consider "7.6 and earlier"), and there is a double space before "did". Please clean this up to avoid shipping typos in release notes.

Suggested change

	In 8.0.0 restoring to a 7.6 and below cluster with `--auto-create-buckets` did not work as we were sending a new setting.
	In 8.0.0, restoring to a 7.6 and earlier cluster with `--auto-create-buckets` did not work as we were sending a new setting.

[Copilot]

The MB-69081 entry uses "i.e" without punctuation and reads like a sentence fragment. Please change to "i.e.," (or rephrase) to match standard usage and improve readability.

Suggested change

	i.e `META().expiration`.
	i.e., `META().expiration`.

[Copilot]

The MB-69083 item lists the problem and triggering conditions but never states the fix/resolution. Release-note entries should include what changed in 8.0.1 (and, if helpful, the user-visible effect).

Suggested change

	and UPDATE STATISTICS has been run on all keyspaces/indexes involved
	and UPDATE STATISTICS has been run on all keyspaces/indexes involved
	+
	The query optimizer has been corrected so that such queries now return the correct results when run on 8.0.1, without requiring any changes to existing queries or indexes.

[Copilot]

This MB-69955 description is a run-on sentence (and has a double space before "when users upgraded"). Please split into clearer sentences and add ending punctuation; also consider using an xref for the WITH RECURSIVE doc link if that is the convention for internal docs.

Suggested change

	This causes a syntax error when a path or subpath’s case-insensitive identifier is named `cycle` when users upgraded to a version that supported the recursive with feature https://docs.couchbase.com/server/current/n1ql/n1ql-language-reference/with-recursive.html[WITH recursive clause]
	This caused syntax errors when a path or subpath’s case-insensitive identifier was named `cycle` when users upgraded to a version that supported the recursive WITH feature. For more information, see https://docs.couchbase.com/server/current/n1ql/n1ql-language-reference/with-recursive.html[WITH RECURSIVE clause].