cockroachdb · ebembi-crdb · May 12, 2026
diff --git a/src/current/advisories/a101963.md b/src/current/advisories/a101963.md
@@ -19,13 +19,13 @@ In the following circumstances, backups that include [revision history](https://
 
 ## Statement
 
-This is resolved in CockroachDB by [#102179](https://github.com/cockroachdb/cockroach/pull/102179), which ensures that `RESTORE` operations can correctly restore from backups that include this incorrect metadata.
+This is resolved in CockroachDB by #102179, which ensures that `RESTORE` operations can correctly restore from backups that include this incorrect metadata.
 
 The fix has been applied to maintenance releases of CockroachDB: [v22.2.9](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-9).
 
 This fix will be applied to maintenance releases of CockroachDB: v22.1.20. Until that version is available, refer to [Mitigation](#mitigation) for a suggested workaround.
 
-This public issue is tracked by [#101963](https://github.com/cockroachdb/cockroach/issues/101963).
+This public issue is tracked by #101963.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a102375.md b/src/current/advisories/a102375.md
@@ -16,13 +16,13 @@ In CockroachDB versions v22.1.19 and v22.2.8, some customers may experience spur
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#102405](https://github.com/cockroachdb/cockroach/issues/102405) which ensures that privilege checks happen after staleness checks when attempting to use the query cache.
+This is resolved in CockroachDB by PR #102405 which ensures that privilege checks happen after staleness checks when attempting to use the query cache.
 
 The fix has been applied to the maintenance release of CockroachDB [v22.2.9](https://www.cockroachlabs.com/docs/releases/v22.2#v22-2-9).
 
 This fix will be applied to the maintenance release of CockroachDB v22.1.20.
 
-This public issue is tracked by [#102375](https://github.com/cockroachdb/cockroach/issues/102375).
+This public issue is tracked by #102375.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a103220.md b/src/current/advisories/a103220.md
@@ -15,11 +15,11 @@ In CockroachDB v23.1.0 and its testing versions, inserting rows into a multi-[co
 
 ## Statement
 
-This is resolved in CockroachDB by PR [103323](https://github.com/cockroachdb/cockroach/pull/103323).
+This is resolved in CockroachDB by PR 103323.
 
 This fix has been applied to maintenance releases of CockroachDB [v23.1.1](https://www.cockroachlabs.com/docs/releases/v23.1#v23-1-1) and later.
 
-This public issue is tracked by [#103220](https://github.com/cockroachdb/cockroach/issues/103220).
+This public issue is tracked by #103220.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a104309.md b/src/current/advisories/a104309.md
@@ -47,7 +47,7 @@ Versions prior to 22.2 are no longer eligible for [maintenance support](https://
 
 ## Statement
 
-This is resolved in CockroachDB by [PR #117612](https://github.com/cockroachdb/cockroach/pull/117612), which uses a barrier command to ensure that all historical and ongoing range writes have been applied to the local replica and emitted before the resolved timestamp is advanced and a checkpoint is emitted.
+This is resolved in CockroachDB by PR #117612, which uses a barrier command to ensure that all historical and ongoing range writes have been applied to the local replica and emitted before the resolved timestamp is advanced and a checkpoint is emitted.
 
 The fix has been applied to maintenance releases of CockroachDB:
 
@@ -63,7 +63,7 @@ However, the initial fix introduced a bug that could cause a rangefeed’s resol
 
 Users are encouraged to upgrade to a version that contains both fixes.
 
-This public issue is tracked by [Issue #104309](https://github.com/cockroachdb/cockroach/issues/104309).
+This public issue is tracked by Issue #104309.
 
 ## Mitigation
 
@@ -90,7 +90,7 @@ If data is found, it can be re-emitted in two ways:
 
 <a id="issue_110536"></a>
 {{site.data.alerts.callout_info}}
-This fix introduces a [bug](https://github.com/cockroachdb/cockroach/issues/119536) that could cause a rangefeed’s resolved timestamp to stop advancing. The corresponding changefeed will appear to be stalled in `RUNNING` state in certain conditions: If a rangefeed is running on a follower on a recently-merged range, and the rangefeed encounters an aborted transaction, then the resolved timestamp may stall. Events such as row updates will still be emitted as normal, but new checkpoints will not be emitted.
+This fix introduces a bug that could cause a rangefeed’s resolved timestamp to stop advancing. The corresponding changefeed will appear to be stalled in `RUNNING` state in certain conditions: If a rangefeed is running on a follower on a recently-merged range, and the rangefeed encounters an aborted transaction, then the resolved timestamp may stall. Events such as row updates will still be emitted as normal, but new checkpoints will not be emitted.
 
 That bug is fixed in the following versions:
 
@@ -120,7 +120,7 @@ If your cluster experiences a stalled rangefeed or changefeed after upgrading, y
 
 As an alternative to avoid disruption to the changefeed, you can temporarily disable `kv.rangefeed.push_txns.barrier.enabled` to disable the fix to this advisory, **a104309**, until a fix to the stalled rangefeed bug is available.
 
-This issue is tracked by [Issue #119536](https://github.com/cockroachdb/cockroach/issues/119536).
+This issue is tracked by Issue #119536.
 {{site.data.alerts.end}}
 
 ## Impact

diff --git a/src/current/advisories/a106617.md b/src/current/advisories/a106617.md
@@ -20,11 +20,11 @@ The corruption is limited to a single store, allowing recovery through [decommis
 
 ## Statement
 
-This is resolved in CockroachDB by [#107249](https://github.com/cockroachdb/cockroach/pull/107249), which fixes the ordering of steps during encryption-at-rest log rotation. 
+This is resolved in CockroachDB by #107249, which fixes the ordering of steps during encryption-at-rest log rotation. 
 
 The fix has been applied to maintenance releases of CockroachDB [v23.1.8](../releases/v23.1.html#v23-1-8), [v22.2.13](../releases/v22.2.html#v22-2-13), v22.1.22.
 
-This public issue is tracked by [#106617](https://github.com/cockroachdb/cockroach/issues/106617).
+This public issue is tracked by #106617.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a110363.md b/src/current/advisories/a110363.md
@@ -22,11 +22,11 @@ This issue affects clusters that meet all of the following conditions:
 
 ## Statement
 
-This is resolved in CockroachDB by [#110364](https://github.com/cockroachdb/cockroach/pull/110364), which prevents deletion of the TTL field upon upgrade.
+This is resolved in CockroachDB by #110364, which prevents deletion of the TTL field upon upgrade.
 
 The fix will be available in CockroachDB v23.1.10.
 
-This public issue is tracked by [#110363](https://github.com/cockroachdb/cockroach/issues/110363).
+This public issue is tracked by #110363.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a114393.md b/src/current/advisories/a114393.md
@@ -20,11 +20,11 @@ A critical bug has been identified in the [optimizer](../v23.1/cost-based-optimi
 
 ## Statement
 
-This is resolved in CockroachDB by [#114394](https://github.com/cockroachdb/cockroach/pull/114394).
+This is resolved in CockroachDB by #114394.
 
 This fix has been applied to maintenance release of CockroachDB [v23.1.13](../releases/v23.1.html#v23-1-13), which fixes a bug that could cause a query plan to skip scanning rows from the local region when performing a lookup join with a `REGIONAL BY ROW` table as the input.
 
-This public issue is tracked by [#114393](https://github.com/cockroachdb/cockroach/issues/114393).
+This public issue is tracked by #114393.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a122372.md b/src/current/advisories/a122372.md
@@ -14,15 +14,15 @@ Publication date: {{ page.advisory_date | date: "%B %e, %Y" }}
 
 In all versions of CockroachDB v23.1, v23.2.0 to v23.2.9, v24.1.0 to v24.1.3, and testing versions of v24.2 through v24.2.0-beta.3, [changefeeds]({% link v24.2/change-data-capture-overview.md %}) could emit events on the same row out of order in some cases, which violates [changefeed ordering guarantees]({% link v24.2/changefeed-messages.md %}#per-key-ordering). This issue was caused by a [bug in the sarama Kafka client library](https://github.com/IBM/sarama/issues/2619), a third-party library that CockroachDB uses to talk to Kafka clusters. The bug manifested when a workload had mutations to the same key in rapid succession, because it was possible for [sarama](https://github.com/IBM/sarama) to re-order the messages if it encountered a retryable Kafka error.
 
-To resolve this issue, CockroachDB now uses a new version of the Kafka sink that uses [franz-go](https://github.com/twmb/franz-go), a different third-party Kafka client library that does not have this bug. The new Kafka sink can be enabled using the cluster setting [`changefeed.new_kafka_sink.enabled`]({% link v24.2/show-cluster-setting.md %}). The new Kafka sink was added in PR [#126213](https://github.com/cockroachdb/cockroach/pull/126213).
+To resolve this issue, CockroachDB now uses a new version of the Kafka sink that uses [franz-go](https://github.com/twmb/franz-go), a different third-party Kafka client library that does not have this bug. The new Kafka sink can be enabled using the cluster setting [`changefeed.new_kafka_sink.enabled`]({% link v24.2/show-cluster-setting.md %}). The new Kafka sink was added in PR #126213.
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#126213](https://github.com/cockroachdb/cockroach/pull/126213), which replaces the Kafka client library [sarama](https://github.com/IBM/sarama) with [franz-go](https://github.com/twmb/franz-go).
+This is resolved in CockroachDB by PR #126213, which replaces the Kafka client library [sarama](https://github.com/IBM/sarama) with [franz-go](https://github.com/twmb/franz-go).
 
 The fix has been applied to maintenance releases of CockroachDB v23.2.10, v24.1.4, and v24.2.0-rc.1.
 
-This public issue is tracked by issue [#122372](https://github.com/cockroachdb/cockroach/issues/122372).
+This public issue is tracked by issue #122372.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a123371.md b/src/current/advisories/a123371.md
@@ -12,7 +12,7 @@ Publication date: {{ page.advisory_date | date: "%B %e, %Y" }}
 
 ## Description
 
-In all versions of CockroachDB v22.2, v23.1.0 to v23.1.21, v23.2.0 to v23.2.5, and testing versions of v24.1 through v24.1.0-rc.1, changefeeds could drop events during the initial scan in some cases, causing changefeed consumers to receive incomplete data. This bug was caused by a [code change](https://github.com/cockroachdb/cockroach/commit/0eda54018b9676f855efcd90bfdd0c486c97bfdd) to reduce the number of duplicates sent during an initial scan if the changefeed needed to restart by using the checkpoint to determine which spans could be skipped when the job resumed. This change led to some non-determinism in another part of the codebase that would sometimes incorrectly forward the progress of every span a node was tracking to the lowest checkpoint timestamp when some spans may not have been scanned yet. This bug is now fixed by [PR #123625](https://github.com/cockroachdb/cockroach/pull/123625).
+In all versions of CockroachDB v22.2, v23.1.0 to v23.1.21, v23.2.0 to v23.2.5, and testing versions of v24.1 through v24.1.0-rc.1, changefeeds could drop events during the initial scan in some cases, causing changefeed consumers to receive incomplete data. This bug was caused by a code change to reduce the number of duplicates sent during an initial scan if the changefeed needed to restart by using the checkpoint to determine which spans could be skipped when the job resumed. This change led to some non-determinism in another part of the codebase that would sometimes incorrectly forward the progress of every span a node was tracking to the lowest checkpoint timestamp when some spans may not have been scanned yet. This bug is now fixed by PR #123625.
 
 Symptoms of the bug:
 
@@ -35,9 +35,9 @@ Factors that increase the likelihood the bug occurring:
 
 ## Statement
 
-This is resolved in CockroachDB by [PR #123625](https://github.com/cockroachdb/cockroach/pull/123625) which prevents incorrect forwarding of progress for spans that have not been scanned yet by the initial scan.
+This is resolved in CockroachDB by PR #123625 which prevents incorrect forwarding of progress for spans that have not been scanned yet by the initial scan.
 The fix has been applied to maintenance releases of CockroachDB v23.1.22, v23.2.6, and v24.1.0-rc.2.
-This public issue is tracked by [#123371](https://github.com/cockroachdb/cockroach/issues/123371).
+This public issue is tracked by #123371.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a131639.md b/src/current/advisories/a131639.md
@@ -35,15 +35,15 @@ Versions prior to 23.1 are no longer eligible for [maintenance support]({% link
 
 ## Statement
 
-[In #123442](https://github.com/cockroachdb/cockroach/commit/6dd54b46cc56b7d2b302e0d5ec1509658a1c86f7), we resolved an issue with CockroachDB in the expiration-to-epoch lease promotion transition process, where a lease's effective expiration could be allowed to regress, resulting in two nodes believing they are the leaseholder for a range.
+In #123442, we resolved an issue with CockroachDB in the expiration-to-epoch lease promotion transition process, where a lease's effective expiration could be allowed to regress, resulting in two nodes believing they are the leaseholder for a range.
 
 The patch has been applied to maintenance releases of CockroachDB:
 
 - [v23.1.27]({% link releases/v23.1.md%}#v23-1-27)
 - [v23.2.11]({% link releases/v23.2.md%}#v23-2-11)
 - [v24.1.1]({% link releases/v24.1.md%}#v24-1-1)
 
-This public issue is tracked by [131639](https://github.com/cockroachdb/cockroach/issues/131639).
+This public issue is tracked by 131639.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a144650.md b/src/current/advisories/a144650.md
@@ -28,9 +28,9 @@ For steps to identify and mitigate affected operations, refer to [Mitigation](#m
 
 ## Statement
 
-This issue is resolved in CockroachDB by [#144646](https://github.com/cockroachdb/cockroach/pull/144646), which disables the rare (async flush) code path for bulk write operations. The fix has been applied to the v23.2.24, v24.1.17, v24.3.11, and v25.1.5 production releases, and to the v25.2.0-beta.2 testing release.
+This issue is resolved in CockroachDB by #144646, which disables the rare (async flush) code path for bulk write operations. The fix has been applied to the v23.2.24, v24.1.17, v24.3.11, and v25.1.5 production releases, and to the v25.2.0-beta.2 testing release.
 
-The issue is tracked publicly by [#144650](https://github.com/cockroachdb/cockroach/issues/144650).
+The issue is tracked publicly by #144650.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a151050.md b/src/current/advisories/a151050.md
@@ -20,11 +20,11 @@ While this issue is expected to occur rarely, we recommend upgrading to the next
 
 ## Statement
 
-This issue is resolved in CockroachDB by PR [#151058](https://github.com/cockroachdb/cockroach/pull/151058) which ensures errors encountered during all buffer flushes - even those caused by intermittent object storage provider errors - are correctly reported to the backup job. 
+This issue is resolved in CockroachDB by PR #151058 which ensures errors encountered during all buffer flushes - even those caused by intermittent object storage provider errors - are correctly reported to the backup job. 
 
 The fix has been applied to the following versions of CockroachDB: v24.1.22, v24.3.17, v25.1.10, v25.2.4, and the testing version of v25.3, v25.3.0-rc.2.
 
-This issue is tracked publicly by [#151050](https://github.com/cockroachdb/cockroach/issues/151050).
+This issue is tracked publicly by #151050.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a161317.md b/src/current/advisories/a161317.md
@@ -26,7 +26,7 @@ This advisory applies to the following versions of CockroachDB:
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#161318](https://github.com/cockroachdb/cockroach/pull/161318) which fixes the improper error handling in the Avro OCF reader implementation.
+This is resolved in CockroachDB by PR #161318 which fixes the improper error handling in the Avro OCF reader implementation.
 
 This fix has been applied to the following maintenance releases of CockroachDB:
 
@@ -35,7 +35,7 @@ This fix has been applied to the following maintenance releases of CockroachDB:
 - v25.4.4
 - Testing release v26.1.0-rc.1
 
-This public issue is tracked in [#161317](https://github.com/cockroachdb/cockroach/issues/161317).
+This public issue is tracked in #161317.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a162085.md b/src/current/advisories/a162085.md
@@ -16,7 +16,7 @@ A race condition between MVCC garbage collection and range splits in CockroachDB
 
 Most workloads are unlikely to be affected by this issue. The conditions that precipitate data loss are narrow and require a specific combination of data lifecycle patterns and timing. Details on how to assess your risk are provided in the *Am I Affected?* section below.
 
-This public issue is tracked by [#162085](https://github.com/cockroachdb/cockroach/issues/162085).
+This public issue is tracked by #162085.
 
 ## Action Required
 
@@ -140,7 +140,7 @@ This section provides a detailed technical explanation of the underlying issue f
 
 ### Background
 
-CockroachDB v23.1 (PR [#90830](https://github.com/cockroachdb/cockroach/pull/90830)) added an optimization to the garbage collection process. When there is a contiguous span of at least 2,000 non-live (obsolete) keys in a range, the GC process writes a Pebble range tombstone using a ClearRange request to efficiently delete this span of data, rather than deleting each key individually.
+CockroachDB v23.1 (PR #90830) added an optimization to the garbage collection process. When there is a contiguous span of at least 2,000 non-live (obsolete) keys in a range, the GC process writes a Pebble range tombstone using a ClearRange request to efficiently delete this span of data, rather than deleting each key individually.
 
 ### The race condition
 

diff --git a/src/current/advisories/a166122.md b/src/current/advisories/a166122.md
@@ -37,7 +37,7 @@ The root cause is in the SQL optimizer, which incorrectly applies two optimizati
 
 ## Statement
 
-This is resolved in CockroachDB by [PR #166123](https://github.com/cockroachdb/cockroach/pull/166123), which fixes the optimizer to always fetch the required columns and avoid simplifying predicate evaluation for mutation indexes.
+This is resolved in CockroachDB by PR #166123, which fixes the optimizer to always fetch the required columns and avoid simplifying predicate evaluation for mutation indexes.
 
 A fix has been applied to the following maintenance releases of CockroachDB:
 
@@ -47,7 +47,7 @@ A fix has been applied to the following maintenance releases of CockroachDB:
 - v26.1.3
 - Testing release v26.2.0-beta.2
 
-This public issue is tracked by [#166122](https://github.com/cockroachdb/cockroach/issues/166122).
+This public issue is tracked by #166122.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a190483.md b/src/current/advisories/a190483.md
@@ -34,11 +34,11 @@ If the result set is empty, no further action is required. If the result set is
 
 ## Statement
 
-This is resolved in CockroachDB by PR [#109713](https://github.com/cockroachdb/cockroach/pull/109713) for v23.1 and PR [#109750](https://github.com/cockroachdb/cockroach/pull/109750) for v22.2. The PRs update the method used to select the boundaries at which ranges of data are split during `RESTORE` to avoid splitting between two column families of the same row.
+This is resolved in CockroachDB by PR #109713 for v23.1 and PR #109750 for v22.2. The PRs update the method used to select the boundaries at which ranges of data are split during `RESTORE` to avoid splitting between two column families of the same row.
 
 These fixes are available in CockroachDB maintenance releases v23.1.9 and v22.2.14.
 
-This public issue is tracked in [109483](https://github.com/cockroachdb/cockroach/issues/109483).
+This public issue is tracked in 109483.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a30821.md b/src/current/advisories/a30821.md
@@ -20,7 +20,7 @@ On October 23rd, 2018, an internal review uncovered a security vulnerability wit
 
 Registered users were informed privately of the issue and provided with early access to the fix, ahead of the public advisory.
 
-This issue is tracked internally as [#30821](https://github.com/cockroachdb/cockroach/issues/30821).
+This issue is tracked internally as #30821.
 
 ## Mitigation
 

diff --git a/src/current/advisories/a42567.md b/src/current/advisories/a42567.md
@@ -26,7 +26,7 @@ This issue was fixed in patch revisions v2.1.10, v19.1.6, and v19.2.2 by requiri
 The issue also exists in versions v2.0.x and prior. However, up to and including version v2.0.x, the HTTP endpoint was not advertised safe for use on non-privileged networks. Additionally, versions v2.0 and prior have reached end-of-life. All users are invited to upgrade to v2.1.10 or, preferably, a later version.
 
 This issue is tracked internally as
-[#42567](https://github.com/cockroachdb/cockroach/issues/42567).
+#42567.
 
 ## Mitigation