Release Notes for v25.3-v25.3.7

src/current/_data/releases.yml

@@ -10177,4 +10177,38 @@
     docker_arm_experimental: false
     docker_arm_limited_access: false
   source: true
-  previous_release: v26.1.0-alpha.2
+  previous_release: v26.1.0-alpha.2
+
+- release_name: v25.3.7
+  major_version: v25.3
+  release_date: '2026-01-09'
+  release_type: Production
+  go_version: go1.25.5
+  sha: 310e203aaf6c24e18181210ea8803e57ecba2e92
+  has_sql_only: true
+  has_sha256sum: true
+  mac:
+    mac_arm: true
+    mac_arm_experimental: true
+    mac_arm_limited_access: false
+  windows: true
+  linux:
+    linux_arm: true
+    linux_arm_experimental: false
+    linux_arm_limited_access: false
+    linux_intel_fips: true
+    linux_arm_fips: false
+  docker:
+    docker_image: cockroachdb/cockroach
+    docker_arm: true
+    docker_arm_experimental: false
+    docker_arm_limited_access: false
+  source: true
+  previous_release: v25.3.6
+  cloud_only: true
+  cloud_only_message_short: 'Available only for select CockroachDB Cloud clusters'
+  cloud_only_message: >
+      This version is currently available only for select
+      CockroachDB Cloud clusters. To request to upgrade
+      a CockroachDB self-hosted cluster to this version,
+      [contact support](https://support.cockroachlabs.com/hc/requests/new).

src/current/_includes/releases/v25.3/v25.3.7.md

@@ -0,0 +1,60 @@
+## v25.3.7
+
+Release Date: January 9, 2026
+
+{% include releases/new-release-downloads-docker-image.md release=include.release %}
+
+<h3 id="v25-3-7-sql-language-changes">SQL language changes</h3>
+
+- Fixed two cases where creation of a routine
+  resolves unnecessary column dependencies, which can prevent drop of the
+  column without first dropping the routine. Here, the unnecessary
+  dependencies are due to references within CHECK constraints, including
+  those for RLS policies and hash-sharded indexes, as well as those in
+  partial index predicates. The fix is gated behind the session setting
+  `use_improved_routine_deps_triggers_and_computed_cols`, which is off by
+  default before 26.1. [#159442][#159442]
+
+<h3 id="v25-3-7-bug-fixes">Bug fixes</h3>
+
+- Fixed a bug where a SQL statement with side effects (e.g., `INSERT`) inside a PL/pgSQL routine could be dropped if it used an `INTO` clause and none of the target variables were referenced. This bug had been present since v23.2. [#158345][#158345]
+- Fixed a bug that could cause incorrect query results when using prepared statements with NULL placeholders. The bug has existed since v21.2 and violated SQL NULL-equality semantics by returning rows with NULL values when the result set should have been empty.
+
+    From v21.2 to v25.3, the bug occurred when all of the following were true:
+
+    - The query was run with an explicit or implicit prepared statement
+    - The query had an equality filter on a placeholder and a UNIQUE column
+    - The column contained NULL values
+    - The placeholder was assigned to NULL during execution
+
+    Starting in v25.4, the requirements were loosened: the column no longer needed to be UNIQUE, and the bug could reproduce if the column was included in any index. [#159069][#159069]
+- Fixed a bug that allowed columns to be dropped despite being referenced by a routine. This could occur when a column was only referenced as a target column in the SET clause of an UPDATE statement within the routine. This fix only applies to newly-created routines. In versions prior to v26.1, the fix must be enabled by setting the session variable `prevent_update_set_column_drop`. [#159442][#159442]
+- Fixed a bug that caused newly-created routines to incorrectly prevent dropping columns that were not directly referenced, most notably columns referenced by computed column expressions. The fix is gated behind the session setting `use_improved_routine_deps_triggers_and_computed_cols`, which is off by default prior to v26.1. [#159442][#159442]
+- Fixes a rare bug that could cause a panic
+  on changefeed startup. [#159547][#159547]
+- Fixed a bug causing a query predicate to be ignored
+  when the predicate is on a column following one or more ENUM columns in an
+  index, the predicate constrains the column to multiple values, and a lookup
+  join to the index is chosen for the query plan. This bug was introduced in
+  24.3.0 and present in all versions since. [#159776][#159776]
+- Fixed a bug where renaming a column that participated in multiple hash-sharded indexes would fail. [#160089][#160089]
+- Fixed a deadlock that could occur when a
+  statistics creation task panicked.
+
+  🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+  Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> [#160583][#160583]
+
+<h3 id="v25-3-7-performance-improvements">Performance improvements</h3>
+
+- `AFTER` triggers now use a cache for descriptor lookups of `TG_TABLE_SCHEMA`, which can significantly reduce trigger planning latency. [#159386][#159386]
+
+
+[#159069]: https://github.com/cockroachdb/cockroach/pull/159069
+[#159547]: https://github.com/cockroachdb/cockroach/pull/159547
+[#159776]: https://github.com/cockroachdb/cockroach/pull/159776
+[#160089]: https://github.com/cockroachdb/cockroach/pull/160089
+[#160583]: https://github.com/cockroachdb/cockroach/pull/160583
+[#159386]: https://github.com/cockroachdb/cockroach/pull/159386
+[#159442]: https://github.com/cockroachdb/cockroach/pull/159442
+[#158345]: https://github.com/cockroachdb/cockroach/pull/158345