diff --git a/src/current/_config_cockroachdb.yml b/src/current/_config_cockroachdb.yml
index 787f34c6185..2f5b1787337 100644
--- a/src/current/_config_cockroachdb.yml
+++ b/src/current/_config_cockroachdb.yml
@@ -1,7 +1,7 @@
baseurl: /docs
-current_cloud_version: v25.1
+current_cloud_version: v25.2
destination: _site/docs
homepage_title: CockroachDB Docs
versions:
- stable: v25.1
- dev: v25.2
+ stable: v25.2
+ dev: v25.2
\ No newline at end of file
diff --git a/src/current/_data/releases.yml b/src/current/_data/releases.yml
index db3a57ddd6b..96cccf4c465 100644
--- a/src/current/_data/releases.yml
+++ b/src/current/_data/releases.yml
@@ -9071,13 +9071,12 @@
a CockroachDB self-hosted cluster to this version,
[contact support](https://support.cockroachlabs.com/hc/requests/new).
-
-- release_name: v25.2.0-rc.1
+- release_name: v25.2.0
major_version: v25.2
- release_date: '2025-05-12'
- release_type: Testing
+ release_date: '2025-05-09'
+ release_type: Production
go_version: go1.23.7
- sha: 4377500860ff39cc5ddf7954079ced214bd788dc
+ sha: TBD
has_sql_only: true
has_sha256sum: true
mac:
@@ -9092,9 +9091,16 @@
linux_intel_fips: true
linux_arm_fips: false
docker:
- docker_image: cockroachdb/cockroach-unstable
+ docker_image: cockroachdb/cockroach
docker_arm: true
docker_arm_experimental: false
docker_arm_limited_access: false
source: true
previous_release: v25.2.0-beta.3
+ 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).
diff --git a/src/current/_data/versions.csv b/src/current/_data/versions.csv
index 3c937caf518..eda70e218da 100644
--- a/src/current/_data/versions.csv
+++ b/src/current/_data/versions.csv
@@ -17,4 +17,4 @@ v24.1,2024-05-20,2025-05-20,2025-11-20,24.1.5,24.1.6,2024-10-21,2025-10-21,2026-
v24.2,2024-08-12,2025-02-12,N/A,N/A,N/A,N/A,N/A,N/A,v24.1,release-24.2,2028-08-12
v24.3,2024-11-18,2025-11-18,2026-05-18,24.3.11,24.3.12,2025-05-05,2026-05-05,2027-05-05,v24.2,release-24.3,N/A
v25.1,2025-02-18,2026-08-18,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-25.1,N/A
-v25.2,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v25.1,release-25.2,N/A
+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,N/A
diff --git a/src/current/_includes/releases/v24.2/feature-detail-key.html b/src/current/_includes/releases/v24.2/feature-detail-key.html
index 3f8cccf7a37..f84c1b185a4 100644
--- a/src/current/_includes/releases/v24.2/feature-detail-key.html
+++ b/src/current/_includes/releases/v24.2/feature-detail-key.html
@@ -7,11 +7,11 @@
★ |
- Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
★★ |
- Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
{% include icon-yes.html %} |
diff --git a/src/current/_includes/releases/v24.3/feature-detail-key.html b/src/current/_includes/releases/v24.3/feature-detail-key.html
index e11ead7e232..95d79284eb4 100644
--- a/src/current/_includes/releases/v24.3/feature-detail-key.html
+++ b/src/current/_includes/releases/v24.3/feature-detail-key.html
@@ -7,11 +7,11 @@
★ |
- Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
★★ |
- Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
{% include icon-yes.html %} |
diff --git a/src/current/_includes/releases/v25.1/feature-detail-key.html b/src/current/_includes/releases/v25.1/feature-detail-key.html
index e11ead7e232..95d79284eb4 100644
--- a/src/current/_includes/releases/v25.1/feature-detail-key.html
+++ b/src/current/_includes/releases/v25.1/feature-detail-key.html
@@ -7,11 +7,11 @@
★ |
- Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
★★ |
- Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
{% include icon-yes.html %} |
diff --git a/src/current/_includes/releases/v25.2/backward-incompatible.md b/src/current/_includes/releases/v25.2/backward-incompatible.md
index 46a1d73ac04..33e6451cfa3 100644
--- a/src/current/_includes/releases/v25.2/backward-incompatible.md
+++ b/src/current/_includes/releases/v25.2/backward-incompatible.md
@@ -1,33 +1,11 @@
-Before [upgrading to CockroachDB v25.1]({% link v25.1/upgrade-cockroach-version.md %}), be sure to review the following backward-incompatible changes, as well as [key cluster setting changes](#v25-1-0-cluster-settings), and adjust your deployment as necessary.
+Before [upgrading to CockroachDB v25.2]({% link v25.2/upgrade-cockroach-version.md %}), be sure to review the following backward-incompatible changes, as well as [key cluster setting changes](#v25-2-0-cluster-settings), and adjust your deployment as necessary.
-- Bullet
+- The default value of the `autocommit_before_ddl` session variable is now `true`. This will cause any schema change statement that is sent during a transaction to make the current transaction commit before executing the schema change in a separate transaction. Users who do not want the autocommit behavior can preserve the previous behavior by changing the default value of `autocommit_before_ddl` with: `ALTER ROLE ALL SET autocommit_before_ddl = false;`. [#139871]
+- `DROP INDEX` can now only be run when `sql_safe_updates` is set to `false`. [#139456]
+- Vector indexes do not support mutation while being created with `CREATE INDEX` or rebuilt with `ALTER PRIMARY KEY`. To prevent inadvertent application downtime, set the `sql_safe_updates` session setting to `false` when using `CREATE INDEX` or `ALTER PRIMARY KEY` with a vector index. [#144601]
+- The variable arguments of polymorphic built-in functions (e.g., `concat`, `num_nulls`, `format`, `concat_ws`, etc.) no longer need to have the same type, matching PostgreSQL behavior. As a result, CockroachDB's type inference engine will no longer be able to infer argument types in some cases where it previously could, and there is a possibility that CockroachDB applications will encounter new errors. The new session variable `use_pre_25_2_variadic_builtins` restores the previous behavior (and limitations). [#144600]
-- Bullet
-
-- Bullet
-
-- Bullet
-
-- Bullet
- - Removed `sql.schema_changer.running`, which is redundant with `jobs.schema_change.currently_running`.
- - Removed `sql.schema_changer.successes`, which is redundant with `jobs.schema_change.resume_completed`.
- - Removed `sql.schema_changer.retry_errors`, which is redundant with `jobs.schema_change.resume_retry_error`.
- - Removed `sql.schema_changer.permanent_errors`, which is redundant with `jobs.schema_change.resume_failed`.
-
-- Bullet
-
- This change is being made because CockroachDB does not have full support for multiple schema changes in a transaction, as described [here]({% link v25.1/online-schema-changes.md %}#schema-changes-within-transactions).
-
- Users who do not desire the autocommit behavior can preserve the old behavior by changing the default value of `autocommit_before_ddl` with a command such as:
-
- ``` ALTER ROLE ALL SET autocommit_before_ddl = false; ```
-
- [#][#]
-
-
-[#]: https://github.com/cockroachdb/cockroach/pull/
-[#]: https://github.com/cockroachdb/cockroach/pull/
-[#]: https://github.com/cockroachdb/cockroach/pull/
-[#]: https://github.com/cockroachdb/cockroach/pull/
-[#]: https://github.com/cockroachdb/cockroach/pull/
-[#]: https://github.com/cockroachdb/cockroach/pull/
\ No newline at end of file
+[#139871]: https://github.com/cockroachdb/cockroach/pull/139871
+[#139456]: https://github.com/cockroachdb/cockroach/pull/139456
+[#144601]: https://github.com/cockroachdb/cockroach/pull/144601
+[#144600]: https://github.com/cockroachdb/cockroach/pull/144600
\ No newline at end of file
diff --git a/src/current/_includes/releases/v25.2/cluster-setting-changes.md b/src/current/_includes/releases/v25.2/cluster-setting-changes.md
index e25eaf685ce..077af0321fa 100644
--- a/src/current/_includes/releases/v25.2/cluster-setting-changes.md
+++ b/src/current/_includes/releases/v25.2/cluster-setting-changes.md
@@ -1,49 +1,15 @@
-Changes to [cluster settings]({% link v25.1/cluster-settings.md %}) should be reviewed prior to upgrading. New default cluster setting values will be used unless you have manually set a value for a setting. This can be confirmed by running the SQL statement `SELECT * FROM system.settings` to view the non-default settings.
+Changes to [cluster settings]({% link v25.2/cluster-settings.md %}) should be reviewed prior to upgrading. New default cluster setting values will be used unless you have manually set a value for a setting. This can be confirmed by running the SQL statement `SELECT * FROM system.settings` to view the non-default settings.
-- Bullet
-- Bullet
-- Bullet
-- Bullet
-- Bullet
+Settings added
-Settings added
+- `feature.vector_index.enabled` - Set to `TRUE` to enable vector indexes. Default is `FALSE` (not enabled).
+- `server.child_metrics.include_aggregate.enabled` - When `TRUE`, reports both aggregate and child Prometheus metrics, which can be helpful for quick top-level insights or backward compatibility, but should be disabled if you’re seeing inflated values in Prometheus queries due to double counting. Defaults to `TRUE`.
+- `ui.default_timezone` - Allows you to set the time zone for displayed timestamps in the DB Console. (Refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration).) Replaces the deprecated [`ui.display_timezone` cluster setting]({% link v25.2/cluster-settings.md %}#setting-ui-display-timezone). If that value had been set, it will automatically be applied to the new setting `ui.default_timezone`, which takes precedence.
+- `server.oidc_authentication.provider.custom_ca` - Supports a custom root CA for verifying certificates while authenticating with an OIDC provider.
+- `sql.stats.automatic_full_collection.enabled` - It is now possible to automatically collect partial table statistics, but disable automatic collection of full table statistics. To do so, change this setting to `FALSE`. It defaults to `TRUE`. In addition to this cluster setting, you can use the table setting `sql_stats_automatic_full_collection_enabled`.
-- Bullet
-
-- Bullet
-
-- Bullet
-
-- Bullet
-
-Settings with changed defaults
-
-- Bullet
-
-- Bullet
-
-- Bullet
-
-- Bullet
-
-Settings with changed visibility
+Settings with changed visibility
The following settings are now marked `public` after previously being `reserved`. Reserved settings are not documented and their tuning by customers is not supported.
-- Bullet
-
-Renamed settings
-
-- Bullet
-
-- Bullet
-
-Additional setting changes
-
-- Bullet
-
-- Bullet
-
-- Bullet
-
-- Bullet
+- `sql.stats.detailed_latency_metrics.enabled` - Percentile latencies are no longer available for **SQL Activity**. The implementation of these percentiles was error-prone and difficult to understand because it was computed differently from the other SQL statistics collected. Customers interested in viewing percentile latencies per statement fingerprint are encouraged to use the experimental per-fingerprint histograms that can be enabled with the `sql.stats.detailed_latency_metrics.enabled` cluster setting. This will enable externalized histogram metrics via the Prometheus scrape endpoint. [#139500](https://github.com/cockroachdb/cockroach/pulls/139500)
diff --git a/src/current/_includes/releases/v25.2/deprecations.md b/src/current/_includes/releases/v25.2/deprecations.md
index 4a0964d1b6e..4e322d50d81 100644
--- a/src/current/_includes/releases/v25.2/deprecations.md
+++ b/src/current/_includes/releases/v25.2/deprecations.md
@@ -1,5 +1,3 @@
-The following deprecations are announced in v25.1.
+The following deprecations are announced in v25.2.
-- Bullet
-
-[#]: https://github.com/cockroachdb/cockroach/pull/
+- The [`ui.display_timezone` cluster setting]({% link v25.2/cluster-settings.md %}#setting-ui-display-timezone) is now deprecated and will be removed in a future release. If it has been set, its value will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. For further detail, refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration).
\ No newline at end of file
diff --git a/src/current/_includes/releases/v25.2/feature-detail-key.html b/src/current/_includes/releases/v25.2/feature-detail-key.html
index e11ead7e232..95d79284eb4 100644
--- a/src/current/_includes/releases/v25.2/feature-detail-key.html
+++ b/src/current/_includes/releases/v25.2/feature-detail-key.html
@@ -7,11 +7,11 @@
★ |
- Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
★★ |
- Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
+ Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. |
{% include icon-yes.html %} |
diff --git a/src/current/_includes/releases/v25.2/feature-highlights-disaster-recovery.html b/src/current/_includes/releases/v25.2/feature-highlights-performance-and-high-availability.html
similarity index 100%
rename from src/current/_includes/releases/v25.2/feature-highlights-disaster-recovery.html
rename to src/current/_includes/releases/v25.2/feature-highlights-performance-and-high-availability.html
diff --git a/src/current/_includes/releases/v25.2/upgrade-finalization.md b/src/current/_includes/releases/v25.2/upgrade-finalization.md
index dded24379fa..e57478607bf 100644
--- a/src/current/_includes/releases/v25.2/upgrade-finalization.md
+++ b/src/current/_includes/releases/v25.2/upgrade-finalization.md
@@ -1,9 +1,5 @@
-During a major-version upgrade, certain features and performance improvements may not be available until the upgrade is finalized. In v25.1, these are:
+During a major-version upgrade, certain features and performance improvements may not be available until the upgrade is finalized. In v25.2, these are:
-- Bullet
-- Bullet
-- Bullet
-- Bullet
- - `SHOW JOBS` is now based on a new mechanism for storing information about the progress and status of running jobs. [#](https://github.com/cockroachdb/cockroach/pull/)
- - `ALTER JOB ... OWNER TO` can now be used to transfer ownership of a job between users/roles. [#](https://github.com/cockroachdb/cockroach/pull/)
- - Users can now always see and control (pause/resume/cancel) jobs that they own. [#](https://github.com/cockroachdb/cockroach/pull/)
+- Row-level security
+- Creating a set-returning PL/pgSQL function
+- Support for the `jsonpath` data type
\ No newline at end of file
diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md
new file mode 100644
index 00000000000..59a2d77406b
--- /dev/null
+++ b/src/current/_includes/releases/v25.2/v25.2.0.md
@@ -0,0 +1,396 @@
+## v25.2.0
+
+Release Date: May 12, 2025
+
+With the release of CockroachDB v25.2, we've added new capabilities to help you migrate, build, and operate more efficiently.
+
+For a summary of the most significant changes, refer to [Feature Highlights](#v25-2-0-feature-highlights).
+
+{% include releases/new-release-downloads-docker-image.md release=include.release %}
+
+Feature highlights
+
+This section summarizes the most significant user-facing changes in v25.2.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v25.2, including bug fixes and performance improvements, refer to the [release notes]({% link releases/index.md %}#testing-releases) for v25.2 testing releases. You can also search the docs for sections labeled [New in v25.2](https://www.cockroachlabs.com/docs/search?query=new+in+v25.2).
+
+- **Feature categories**
+ - [CockroachDB Cloud](#v25-2-0-cloud)
+ - [Performance and High Availability](#v25-2-0-performance-ha)>
+ - [Change Data Capture](#v25-2-0-change-data-capture)
+ - [Observability](#v25-2-0-observability)
+ - [Security](#v25-2-0-security)
+ - [SQL](#v25-2-0-sql)
+ - [Licensing](#v25-2-0-licensing)
+
+- **Additional information**
+ - [Backward-incompatible changes](#v25-2-0-backward-incompatible-changes)
+ - [Key cluster setting changes](#v25-2-0-key-cluster-setting-changes)
+ - [Deprecations] (#v25-2-0-deprecations)
+ - [Known limitations](#v25-2-0-known-limitations)
+ - [Additional resources](#v25-2-0-additional-resources)
+
+
+
+
CockroachDB Cloud
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Organize your cloud resources with labels
+
+ You can categorize your clusters & folders with custom key-value labels. Use labels to add metadata to your clusters, such as environments, teams, or applications.
+
+ |
+ All* |
+ {% include icon-no.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+
+
+
+ Switch between Basic and Standard plans in the Cloud Console
+
+ You can now change cluster plans between Basic and Standard from the CockroachDB Cloud Console.
+
+ |
+ All* |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+
+
+
+
+
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Logical Data Replication is now Generally Available (GA)
+
+ Logical Data Replication (LDR) enables asynchronous data replication between CockroachDB clusters. LDR supports active-active deployments, allowing both source and destination clusters to serve traffic simultaneously, making it ideal for 2DC architectures, low-latency reads/writes, multi-cloud strategies, and workload isolation. For more information, refer to the latest documentation and an earlier blog post.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+
+
+
+
+
Change Data Capture
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Major Reduction in Duplicate Messages for Changefeeds
+
+ A major improvement to changefeeds significantly reduces the number of duplicate messages emitted during restarts and retries. This means more accurate data delivery, lower processing overhead for downstream consumers, and a smoother experience overall. This improvement is especially beneficial in systems with large tables or uneven processing speeds, where legacy checkpointing often led to unnecessary message duplication.
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+
+
+
+ Enriched Changefeed format for easier integration and richer metadata
+
+ An enriched changefeed format has been introduced in Preview that aligns with the Debezium message structure, making it significantly easier to integrate CockroachDB into existing CDC pipelines. This new format adds structured metadata and flexibility to the changefeed message body, allowing seamless migrations from PostgreSQL or Debezium-based systems without re-architecting downstream services. Whether you're working with real-time analytics, event-driven systems, or audit logs, the enriched format provides clear context about each change event, including source information, schema, operation type, and timestamps. It simplifies debugging, enhances observability, and makes changefeeds more useful in complex, distributed architectures.
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+
+
+
+
+
Observability
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Additional logs and metrics to identify and detect hotspots.
+
+ In 25.2.1, additional logs and metrics will be available to help you detect performance hotspots. During high CPU load, range logs will be emitted more frequently to the Ops channel, with added fields that highlight potential hot row and index scenarios.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+
+
+
+ Configure DB Console to display timestamps in any time zone
+
+ Using a new cluster setting, you can now configure DB Console to display timestamps in any time zone. If the former cluster setting was set, its value is applied to the new setting when you upgrade to v25.2. For details, refer to DB Console Timezone Configuration).
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+
+
+
+ Multi-dimensional metrics
+
+ In v25.2.1, multi-dimensional metrics by application name and database name will be available in Preview, enabling you to segment and track critical SQL metrics by database or application.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+
+
+
+
+
Security
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Configurable TLS cipher suite restrictions
+
+ A new cockroach start flag, --tls-cipher-suites , allows administrators to restrict which supported TLS cipher suites are permitted for incoming SQL, RPC, and HTTP connections. Connections using disallowed cipher suites are rejected and logged. The restriction applies to both TLS 1.2 and TLS 1.3, enabling tighter control over cryptographic standards in secure clusters.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+
+
+
+ Row-Level Security
+
+ Controlling who can access what data is more important than ever as organizations scale and modernize their data infrastructure. As enterprises move to modernize their critical databases, they need fine-grained, built-in access controls that go beyond table-level permissions. That’s why, with the 25.2 release of CockroachDB, we’re introducing Row-Level Security — a powerful feature that allows you to define and enforce access policies at the row level, directly within the database. This form of mandatory access control enables developers and operators to tightly govern data visibility based on user roles or attributes — making it a natural fit for securing sensitive workloads and building robust multi-tenant applications. With row-level security, CockroachDB makes it simple to isolate data, comply with regulatory requirements, and reduce application-side complexity — all while maintaining performance at scale and with minimal application changes.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+
+
+
+
+
SQL
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Faster index creation on large tables
+
+ Schema change operations such as index creations are now up to 30% faster based on our testing with a sample workload on a 1TB table.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+
+
+
+ Vector Indexing available in Preview
+
+ CockroachDB now offers vector indexing in preview, enabling efficient storage and similarity search over high-dimensional data. This feature simplifies building recommendation engines, semantic search, and other machine-learning workflows directly in the database—letting you prototype and integrate advanced vector-based applications without external tooling while taking advantage of powerful SQL semantics.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+
+
+
+ JSONPath support in Preview
+
+ Preview support for JSONPath enables powerful, declarative querying and manipulation of deeply nested JSON structures. This makes it easier to work with complex JSON data and prototype advanced JSON-based workflows.
+
+ |
+ 25.2 |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+ {% include icon-yes.html %} |
+
+
+
+
+
Licensing
+
+
+
+
+ Feature |
+ Availability |
+
+
+ Ver. |
+ Self-hosted |
+ Advanced |
+ Standard |
+ Basic |
+
+
+
+
+
+ Manage Enterprise license keys in the Cloud Console
+
+ You can now manage new Enterprise license keys for self-hosted CockroachDB clusters in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications.
+ |
+ All* |
+ {% include icon-yes.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+ {% include icon-no.html %} |
+
+
+
+
+{% include releases/v25.2/feature-detail-key.html %}
+
+
+
+
+
+Backward-incompatible changes
+
+{% include releases/v25.2/backward-incompatible.md %}
+
+
+
+Features that Require Upgrade Finalization
+
+{% include releases/v25.2/upgrade-finalization.md %}
+
+
+
+Key Cluster Setting Changes
+
+{% include releases/v25.2/cluster-setting-changes.md %}
+
+
+
+Deprecations
+
+{% include releases/v25.2/deprecations.md %}
+
+Known limitations
+
+For information about new and unresolved limitations in CockroachDB v25.2, with suggested workarounds where applicable, refer to [Known Limitations]({% link v25.2/known-limitations.md %}).
+
+Additional resources
+
+Resource | Topic | Description
+---------------------+--------------------------------------------+-------------
+Cockroach University | [Introduction to Distributed SQL and CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+intro-to-distributed-sql-and-cockroachdb+self-paced/about) | This course introduces the core concepts behind distributed SQL databases and describes how CockroachDB fits into this landscape. You will learn what differentiates CockroachDB from both legacy SQL and NoSQL databases and how CockroachDB ensures consistent transactions without sacrificing scale and resiliency. You'll learn about CockroachDB's seamless horizontal scalability, distributed transactions with strict ACID guarantees, and high availability and resilience.
+Cockroach University | [Practical First Steps with CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+practical-first-steps-with-crdb+self-paced/about) | This course will give you the tools you need to get started with CockroachDB. During the course, you will learn how to spin up a cluster, use the Admin UI to monitor cluster activity, and use SQL shell to solve a set of hands-on exercises.
+Cockroach University | [Enterprise Application Development with CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+client-side-txn-handling+self-paced/about) | This course is the first in a series designed to equip you with best practices for mastering application-level (client-side) transaction management in CockroachDB. We'll dive deep on common differences between CockroachDB and legacy SQL databases and help you sidestep challenges you might encounter when migrating to CockroachDB from Oracle, PostgreSQL, and MySQL.
+Cockroach University | [Building a Highly Resilient Multi-region Database using CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+intro-to-resilience-in-multi-region+self-paced/about) | This course is part of a series introducing solutions to running low-latency, highly resilient applications for data-intensive workloads on CockroachDB. In this course we focus on surviving large-scale infrastructure failures like losing an entire cloud region without losing data during recovery. We'll show you how to use CockroachDB survival goals in a multi-region cluster to implement a highly resilient database that survives node or network failures across multiple regions with zero data loss.
+Docs | [Migration Overview]({% link v25.2/migration-overview.md %}) | This page summarizes the steps of migrating a database to CockroachDB, which include testing and updating your schema to work with CockroachDB, moving your data into CockroachDB, and testing and updating your application.
+Docs | [Architecture Overview](https://www.cockroachlabs.com/docs/v25.2/architecture/overview) | This page provides a starting point for understanding the architecture and design choices that enable CockroachDB's scalability and consistency capabilities.
+Docs | [SQL Feature Support]({% link v25.2/sql-feature-support.md %}) | The page summarizes the standard SQL features CockroachDB supports as well as common extensions to the standard.
+Docs | [Change Data Capture Overview]({% link v25.2/change-data-capture-overview.md %}) | This page summarizes CockroachDB's data streaming capabilities. Change data capture (CDC) provides efficient, distributed, row-level changefeeds into a configurable sink for downstream processing such as reporting, caching, or full-text indexing.
+Docs | [Backup Architecture]({% link v25.2/backup-architecture.md %}) | This page describes the backup job workflow with a high-level overview, diagrams, and more details on each phase of the job.
diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md
index b326971b2e3..25ee9aeb43d 100644
--- a/src/current/releases/cloud.md
+++ b/src/current/releases/cloud.md
@@ -14,6 +14,14 @@ Get future release notes emailed to you:
{% include marketo.html formId=1083 %}
+## May 12, 2025
+
+CockroachDB v25.2 is now generally available (GA) for CockroachDB Cloud {{ site.data.products.advanced }} clusters. CockroachDB v25.2 is a [Regular release]({% link releases/index.md %}#release-types).
+
+For release notes, refer to [What's New in v25.2]({% link releases/v25.2.md %}).
+
+To get started with v25.2, refer to [Create a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/create-an-advanced-cluster.md %}) or [Upgrade a Cluster in CockroachDB Cloud]({% link cockroachcloud/upgrade-cockroach-version.md %}).
+
## April 30, 2025
You can now use the CockroachDB {{ site.data.products.cloud }} Console to [edit the labels of a cluster or folder]({% link cockroachcloud/labels.md %}).
diff --git a/src/current/releases/index.md b/src/current/releases/index.md
index 17c1a81355a..b5763109508 100644
--- a/src/current/releases/index.md
+++ b/src/current/releases/index.md
@@ -23,10 +23,6 @@ indented in relation to the other Liquid. Please try to keep the indentation con
## Overview
-{{site.data.alerts.callout_info}}
-{% include common/license/evolving.md %}
-{{site.data.alerts.end}}
-
This page explains the types and naming of CockroachDB releases and provides access to the release notes and downloads for all CockroachDB [releases](#downloads).
A new major version of CockroachDB is released quarterly. After a series of testing releases, each major version receives an initial production release, followed by a series of patch releases.
@@ -113,6 +109,7 @@ As of 2024, CockroachDB is released under a staged delivery process. New release
| Version | Release Type | GA date |
| :---: | :---: | :---: |
+| [v25.2](#v25-2) | Regular | 2025-05-12 |
| [v25.1](#v25-1) | Innovation | 2025-02-18 |
| [v24.3](#v24-3) | Regular | 2024-11-18 |
| [v24.2]({% link releases/unsupported-versions.md %}#v24-2) | Innovation | 2024-08-12 |
@@ -126,11 +123,10 @@ The following releases and their descriptions represent proposed plans that are
| Version | Release Type | Expected GA date |
| :---: | :---: | :---: |
-| v25.2 | Regular | 2025 Q2 |
| v25.3 | Innovation | 2025 Q3 |
| v25.4 | Regular | 2025 Q4 |
| v26.1 | Innovation | 2026 Q1 |
-
+| v26.2 | Regular | 2026 Q2 |
## Downloads
@@ -715,7 +711,8 @@ All binaries available on this page released prior to the release date of 24.3.0
To review the CCL, refer to the [CockroachDB Community License](https://www.cockroachlabs.com/cockroachdb-community-license) page. You can find the applicable Business Source License or third party licenses by reviewing these in the `licenses` folder for the applicable version of CockroachDB in the GitHub repository [cockroachdb/cockroach](https://github.com/cockroachdb/cockroach). See individual files for details.
-## Unsupported versions
+In late 2024, Cockroach Labs retired its Core offering to consolidate on a single CockroachDB Enterprise offering under the CockroachDB Software License. This license is available at no charge for individual users and small businesses, and offers all users, free and paid, the full breadth of CockroachDB capabilities. For details, refer to the [CockroachDB licensing update](https://www.cockroachlabs.com/enterprise-license-update/) and [Licensing FAQs]({% link {{site.versions["stable"]}}/licensing-faqs.md %}).
-Release notes for unsupported CockroachDB versions are found on [Unsupported Versions]({% link releases/unsupported-versions.md %}).
+## Unsupported versions
+Release notes for CockroachDB versions that are no longer supported are available on the [Unsupported Versions]({% link releases/unsupported-versions.md %}) page.