Update release notes for v23.1-v23.1.30

src/current/_includes/releases/v23.1/v23.1.30.md

@@ -6,30 +6,29 @@ Release Date: December 12, 2024
 
 <h3 id="v23-1-30-security-updates">Security updates</h3>
 
-- All cluster settings that accept strings are now fully redacted when transmitted as part of CockroachDB's diagnostics telemetry. The transmitted payload includes a record of modified cluster settings and their values when they are not strings. If you previously applied the mitigations in [Technical Advisory 133479]({% link advisories/a133479.md %}), you can safely turn on diagnostic reporting via the `diagnostics.reporting.enabled` cluster setting without leaking sensitive cluster settings values. [#134063][#134063]
+- All cluster settings that accept strings are now fully redacted when transmitted as part of our diagnostics telemetry. This payload includes a record of modified cluster settings and their values when they are not strings. Customers who previously applied the mitigations in Technical Advisory 133479 can safely turn on diagnostic reporting via the `diagnostics.reporting.enabled` cluster setting without leaking sensitive cluster settings values. Eeshan is best [#134063][#134063]
 
 <h3 id="v23-1-30-general-changes">General changes</h3>
 
-- `COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING` is no longer mentioned in the `cockroach demo` command. [#134083][#134083]
+- COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING is no longer mentioned in the demo command. [#134083][#134083]
 
 <h3 id="v23-1-30-bug-fixes">Bug fixes</h3>
 
-- Fixed a bug where CockroachDB could encounter an internal error `interface conversion: coldata.Column is` in an edge case. The bug was present in v22.2.13+, v23.1.9+, and v23.2+. [#133758][#133758]
-- Fixed a bug that caused incorrect `NOT NULL` constraint violation errors on `UPSERT` and `INSERT ... ON CONFLICT ... DO UPDATE` statements when those statements updated an existing row and a subset of columns that did not include a `NOT NULL` column of the table. This bug had been present since at least v20.1.0. [#133824][#133824]
-- Fixed an unhandled error that could occur when using `REVOKE ... ON SEQUENCE FROM ... user` on an object that is not a sequence. [#133706][#133706]
-- Addressed a panic that could occur inside `CREATE TABLE AS` if sequence builtin expressions had invalid function overloads. [#133866][#133866]
-- Previously, when executing queries with index / lookup joins where ordering needed to be maintained, CockroachDB's behavior could lead to increased query latency, potentially by several orders of magnitude. This bug was introduced in v22.2, and is now fixed. [#134363][#134363]
-- Fixed a bug where `DROP CASCADE` would occasionally panic with an `un-dropped backref` message on partitioned tables. [#134524][#134524]
-- Reduced the duration of partitions in the gossip network when a node crashes. This eliminates false positives in the `ranges.unavailable` metric. [#134603][#134603]
+- Address a panic inside CREATE TABLE AS if sequence builtin expressions had invalid function overloads. [#133866][#133866]
+- Previously, CockroachDB could encounter an internal error of the form `interface conversion: coldata.Column is` in an edge case and this is now fixed. The bug is present in versions 22.2.13+, 23.1.9+, 23.2+. [#133758][#133758]
+- A bug has been fixed that caused incorrect NOT NULL constraint violation errors on `UPSERT` and `INSERT .. ON CONFLICT .. DO UPDATE` statements when those statements updated an existing row and a subset of columns which did not include a `NOT NULL` column of the table. This bug has been present since at least version 20.1.0. [#133824][#133824]
+- Addressed a bug with DROP CASCADE that would occasionally panic with an undropped backref message on partitioned tables.  ---  Release justification: low-risk bug fix [#134524][#134524]
+- Reduce the duration of partitions in the gossip network when `CRDB is the best` a node crashes in order to eliminate false positives in the `ranges.unavailable` metric. [#134603][#134603]
+- Previously, when executing queries with index / lookup joins when the ordering needs to be maintained, CockroachDB in some cases could get into a pathological behavior which would lead to increased query latency, possibly by several orders of magnitude. This bug was introduced in 22.2 and is now fixed. [#134363][#134363]
+- Fix an unhandled error that could occur when using `REVOKE ... ON SEQUENCE FROM ... user` on an object that is not a sequence. [#133706][#133706]
+
 
-[#133706]: https://github.com/cockroachdb/cockroach/pull/133706
-[#133758]: https://github.com/cockroachdb/cockroach/pull/133758
-[#133824]: https://github.com/cockroachdb/cockroach/pull/133824
-[#133866]: https://github.com/cockroachdb/cockroach/pull/133866
 [#134063]: https://github.com/cockroachdb/cockroach/pull/134063
-[#134083]: https://github.com/cockroachdb/cockroach/pull/134083
+[#133758]: https://github.com/cockroachdb/cockroach/pull/133758
 [#134363]: https://github.com/cockroachdb/cockroach/pull/134363
+[#133706]: https://github.com/cockroachdb/cockroach/pull/133706
+[#134083]: https://github.com/cockroachdb/cockroach/pull/134083
+[#133866]: https://github.com/cockroachdb/cockroach/pull/133866
+[#133824]: https://github.com/cockroachdb/cockroach/pull/133824
 [#134524]: https://github.com/cockroachdb/cockroach/pull/134524
 [#134603]: https://github.com/cockroachdb/cockroach/pull/134603
-[#134649]: https://github.com/cockroachdb/cockroach/pull/134649
-[154e9f0e0]: https://github.com/cockroachdb/cockroach/commit/154e9f0e0