Release Notes for v26.1-v26.1.0-beta.1

src/current/_data/releases.yml

@@ -10011,3 +10011,199 @@
     docker_arm_limited_access: false
   source: true
   previous_release: v25.4.0
+
+
+- release_name: v26.1.0-alpha.2
+  major_version: v26.1
+  release_date: '2025-12-11'
+  release_type: Testing
+  go_version: go1.25.3
+  sha: 7991c17b6f2957e381666bf13d6405c8037f46c1
+  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-unstable
+    docker_arm: true
+    docker_arm_experimental: false
+    docker_arm_limited_access: false
+  source: true
+  previous_release: v26.1.0-alpha.1
+
+
+- release_name: v25.4.2
+  major_version: v25.4
+  release_date: '2025-12-12'
+  release_type: Production
+  go_version: go1.25.3
+  sha: fed2b8351ac420fec6a1eecce0c78e3848d11896
+  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.4.1
+  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).
+
+
+- release_name: v25.3.6
+  major_version: v25.3
+  release_date: '2025-12-12'
+  release_type: Production
+  go_version: go1.25.3
+  sha: 86392cec66fd0b9851358fa76a6f0aac1d691a84
+  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.5
+  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).
+
+
+- release_name: v25.2.10
+  major_version: v25.2
+  release_date: '2025-12-12'
+  release_type: Production
+  go_version: go1.25.3
+  sha: a2cf0e12d277179df853e7e494c0155a6839edf3
+  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.2.9
+  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).
+
+
+- release_name: v24.3.24
+  major_version: v24.3
+  release_date: '2025-12-12'
+  release_type: Production
+  go_version: go1.25.3
+  sha: dab6bfcdbefef7b4ecc62cb75198e475cbf6778d
+  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: v24.3.23
+  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).
+
+
+- release_name: v26.1.0-beta.1
+  major_version: v26.1
+  release_date: '2025-12-17'
+  release_type: Testing
+  go_version: go1.25.3
+  sha: e15b1ecc444676ba53266770e0b758de9ae72d22
+  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-unstable
+    docker_arm: true
+    docker_arm_experimental: false
+    docker_arm_limited_access: false
+  source: true
+  previous_release: v26.1.0-alpha.2

src/current/_data/versions.csv

@@ -20,4 +20,4 @@ v25.1,2025-02-18,2025-08-18,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-25.1,2029-02-1
 v25.2,2025-05-09,2026-05-12,2026-11-12,N/A,N/A,N/A,N/A,N/A,v25.1,release-25.2,2029-05-09
 v25.3,2025-08-04,2026-02-04,N/A,N/A,N/A,N/A,N/A,N/A,v25.2,release-25.3,2029-08-04
 v25.4,2025-11-03,2026-11-03,2027-05-03,N/A,N/A,N/A,N/A,N/A,v25.3,release-25.4,2029-11-03
-v26.1,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v25.4,release-25.4,N/A
+v26.1,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v25.4,release-26.1,N/A

src/current/_includes/releases/v26.1/v26.1.0-beta.1.md

@@ -0,0 +1,112 @@
+## v26.1.0-beta.1
+
+Release Date: December 17, 2025
+
+{% include releases/new-release-downloads-docker-image.md release=include.release %}
+
+<h3 id="v26-1-0-beta-1-security-updates">Security updates</h3>
+
+- We are adding a new flag
+   `--allow-debug-user` to the cockroach start command to explicitly allow
+   enabling the debug_user to log into the system. This flag is currently
+   experimental and is disabled by default. When not set, authentication
+   attempts by `debug_user` will be rejected with an error: `"certificate
+   authentication failed for user "debug_user""` for SQL connections and
+   `"failed to perform RPC, as debug_user login is not allowed"` for RPC
+   connections.
+
+   This flag is intended for debugging and troubleshooting purposes and should
+   only be enabled when necessary for diagnostic operations. The debug_user
+   should be disabled when not actively in use.
+
+   Note: Certificates must include "debug_user" as one of the principals
+   (CommonName or SubjectAlternativeName) for this functionality. The flag
+   controls whether such certificates are accepted for both SQL client
+   connections and RPC connections. [#158963][#158963]
+
+<h3 id="v26-1-0-beta-1-{{-site.data.products.enterprise-}}-edition-changes">{{ site.data.products.enterprise }} edition changes</h3>
+
+- Improved the description of the
+  changefeed.default_range_distribution_strategy cluster setting to better
+  explain the available options and their behavior.
+
+  Epic: None [#158602][#158602]
+
+<h3 id="v26-1-0-beta-1-sql-language-changes">SQL language changes</h3>
+
+- `crdb_internal.index_usage_stats` and `crdb_internal.datums_to_bytes` are now available in the `information_schema` system catalog as `information_schema.crdb_index_usage_stats` and `information_schema.crdb_datums_to_bytes`, respectively. [#156963][#156963]
+- The `ALTER COLUMN ...` sequence identity
+  commands are run by the declarative schema changer. [#157030][#157030]
+- Added support for `EXECUTE SCHEDULE {schedule_id}` to allow immediate execution of a scheduled job. This does not apply to `ALTER BACKUP SCHEDULE`; attempting to execute a backup schedule will result in an error. [#158694][#158694]
+- `CREATE TYPE` with composite type syntax now supports array types in field definitions. For example, `CREATE TYPE t AS (a INT[])` and `CREATE TYPE t AS (a INT ARRAY)` now work correctly, matching PostgreSQL behavior. [#158888][#158888]
+- introduces the new STRICT option for locality aware
+  backups. When this flag is passed, the backup will fail if we attempt to backup
+  data that lives in a kv node with locality tag X into a bucket with a different
+  locality tag. [#158999][#158999]
+- adds STRICT STORAGE LOCALITY option to backup cmd.
+  Subsequent commit hooks it up to backup flow. [#158999][#158999]
+- CREATE CHANGEFEED FOR DATABASE statement will
+  return an error stating that the feature is not implemented. [#159000][#159000]
+- The `WITH RESOLVED TIMESTAMP` option can be passed to `SHOW JOBS` or `SHOW JOB` to include the resolved timestamp, if any, for the jobs in the output columns. [#159068][#159068]
+
+<h3 id="v26-1-0-beta-1-command-line-changes">Command-line changes</h3>
+
+- You can now specify a user-defined database user when generating `debug zip` and `debug tsdump` files. Use the `--user` and `--url` flags to set the username. Previously, these operations required the root user. This change provides backward compatibility by defaulting the username to `root`. This update is part of an ongoing effort to limit root user access. [#158961][#158961]
+
+<h3 id="v26-1-0-beta-1-bug-fixes">Bug fixes</h3>
+
+- Fixed a bug where issuing a noop schedule modification
+  could skip the next incremental backup
+
+  Fixes: #158296 [#158820][#158820]
+- Fixed a bug that allowed a column to be dropped from
+  its table despite being referenced by a routine. The bug could happen when the
+  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`. [#158935][#158935]
+- Fixed a bug that caused routines to prevent
+  dropping more columns than necessary, 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. [#158935][#158935]
+- A bug has been fixed which could cause incorrect
+  results. The bug has existed since v21.2. From v21.2 up to v25.3, the
+  bug only presented 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.
+  In this case, the query could return rows in which the column's value is
+  NULL, which violates SQL NULL-equality semantics. The correct result set
+  should always be empty.
+  Starting in v25.4, the requirements were loosened slightly. It was no
+  longer necessary for the column to be UNIQUE. The bug could reproduce if
+  the column was included in any index. [#159001][#159001]
+- Fixed a bug where the `schema_locked` table storage parameter could be bypassed by combining `SET (schema_locked=false)` with other schema changes in the same `ALTER TABLE` statement using comma syntax. Schema-locked tables now correctly reject such combined statements. [#159017][#159017]
+
+<h3 id="v26-1-0-beta-1-performance-improvements">Performance improvements</h3>
+
+- Triggers now perform the descriptor lookup for `TG_TABLE_SCHEMA` against a cache. This can significantly reduce trigger planning latency in multi-region databases. [#144217][#144217]
+- After triggers now perform the
+  descriptor lookup for `TG_TABLE_SCHEMA` against a cache. This can
+  significantly reduce trigger planning latency. [#158708][#158708]
+
+
+[#158999]: https://github.com/cockroachdb/cockroach/pull/158999
+[#159068]: https://github.com/cockroachdb/cockroach/pull/159068
+[#158820]: https://github.com/cockroachdb/cockroach/pull/158820
+[#158935]: https://github.com/cockroachdb/cockroach/pull/158935
+[#159001]: https://github.com/cockroachdb/cockroach/pull/159001
+[#158708]: https://github.com/cockroachdb/cockroach/pull/158708
+[#158888]: https://github.com/cockroachdb/cockroach/pull/158888
+[#158694]: https://github.com/cockroachdb/cockroach/pull/158694
+[#144217]: https://github.com/cockroachdb/cockroach/pull/144217
+[#156963]: https://github.com/cockroachdb/cockroach/pull/156963
+[#158602]: https://github.com/cockroachdb/cockroach/pull/158602
+[#157030]: https://github.com/cockroachdb/cockroach/pull/157030
+[#159000]: https://github.com/cockroachdb/cockroach/pull/159000
+[#158961]: https://github.com/cockroachdb/cockroach/pull/158961
+[#159017]: https://github.com/cockroachdb/cockroach/pull/159017
+[#158963]: https://github.com/cockroachdb/cockroach/pull/158963