Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions modules/release-notes/pages/relnotes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@
:page-toclevels: 2
:stem:

include::partial$docs-server-7.6.12-release-notes.adoc[]

include::partial$docs-server-7.6.11-release-notes.adoc[]

include::partial$docs-server-7.6.10-release-notes.adoc[]
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
[#release-7-6-12]
== Release 7.6.12 (May 2026)

Couchbase Server 7.6.12 was released in May 2026.
This maintenance release contains fixes to issues.

=== Cluster Manager

[#table-7-6-12-Cluster-Manager, cols="1,3,1"]
|===
| Issue | Description | Resolution

| https://jira.issues.couchbase.com/browse/MB-65348[MB-65348]
| Couchbase Server adds a Content-Type header to the Prometheus /metrics endpoint.
The endpoint now includes the PrometheusText0.0.4 header value.
This improvement ensures better compatibility with Prometheus scrape points.
| Issue Resolved
|===

=== Analytics Service

[#table-7-6-12-Analytics-Service, cols="1,3,1"]
|===
| Issue | Description | Resolution

| https://jira.issues.couchbase.com/browse/MB-71453[MB-71453]
| Queries combining a LIMIT clause with an index-nested-loop join hint now return correct results.
The Analytics Service pushed the LIMIT to the index search without evaluating all filter conditions.
This fix ensures the service evaluates the complete condition before applying the LIMIT.
| Issue Resolved
|===

=== XDCR

[#table-7-6-12-XDCR, cols='1,3,1']
|===
| Issue | Description | Resolution

| https://jira.issues.couchbase.com/browse/MB-71258[MB-71258]
| Pausing or deleting a replication no longer causes `go` routines to stick indefinitely.
A race condition occurred during rollbacks to zero after cluster fail-overs.
This fix resolves the deadlock and improves replication management stability.
| Issue Resolved
|===