From 9e3ac11064ded984060407f45b313f20b5f45b09 Mon Sep 17 00:00:00 2001 From: Peach Leach Date: Tue, 27 Jan 2026 15:44:29 -0500 Subject: [PATCH 1/7] Added info on the STRICT flag Added info on the STRICT flag --- src/current/_includes/v26.1/backups/backup-options.md | 3 ++- src/current/v26.1/take-and-restore-locality-aware-backups.md | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/src/current/_includes/v26.1/backups/backup-options.md b/src/current/_includes/v26.1/backups/backup-options.md index a4c3eeae595..c42a7366e79 100644 --- a/src/current/_includes/v26.1/backups/backup-options.md +++ b/src/current/_includes/v26.1/backups/backup-options.md @@ -5,4 +5,5 @@ `detached` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | When a backup runs in `detached` mode, it will execute asynchronously. The job ID will be returned after the backup [job creation]({% link {{ page.version.version }}/backup-architecture.md %}#job-creation-phase) completes. Note that with `detached` specified, further job information and the job completion status will not be returned. For more on the differences between the returned job data, see the [example]({% link {{ page.version.version }}/backup.md %}#run-a-backup-asynchronously). To check on the job status, use the [`SHOW JOBS`](show-jobs.html) statement. Backups running on a [schedule](create-schedule-for-backup.html) have the `detached` option applied implicitly.

To run a backup within a [transaction](transactions.html), use the `detached` option. `EXECUTION LOCALITY` | Key-value pairs | Restricts the execution of the backup to nodes that match the defined locality filter requirements. For example, `WITH EXECUTION LOCALITY = 'region=us-west-1a,cloud=aws'`.

Refer to [Take Locality-restricted backups]({% link {{ page.version.version }}/take-locality-restricted-backups.md %}) for usage and reference detail. `kms` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | The URI of the cryptographic key stored in a key management service (KMS), or a comma-separated list of key URIs, used to [take and restore encrypted backups]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples). Refer to [URI Formats]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#uri-formats). The key or keys are used to encrypt the manifest and data files that the `BACKUP` statement generates and to decrypt them during a [restore]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples) operation, and to list the contents of the backup when using [`SHOW BACKUP`]({% link {{ page.version.version }}/show-backup.md %}).

AWS KMS, Google Cloud KMS, and Azure Key Vault are supported. -`incremental_location` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | Create an incremental backup in a different location than the default incremental backup location.

`WITH incremental_location = 'explicit_incrementals_URI'`

See [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations) for usage. \ No newline at end of file +`incremental_location` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | Create an incremental backup in a different location than the default incremental backup location.

`WITH incremental_location = 'explicit_incrementals_URI'`

See [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations) for usage. +`STRICT` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | A backup that runs in `STRICT` mode fails if it attempts to back up data from a key-value node with a particular locality tag to a bucket with a different locality tag. \ No newline at end of file diff --git a/src/current/v26.1/take-and-restore-locality-aware-backups.md b/src/current/v26.1/take-and-restore-locality-aware-backups.md index c86e24b057e..ddccd25baa9 100644 --- a/src/current/v26.1/take-and-restore-locality-aware-backups.md +++ b/src/current/v26.1/take-and-restore-locality-aware-backups.md @@ -45,6 +45,8 @@ When you run the `BACKUP` statement for a locality-aware backup, check the follo - {% include {{ page.version.version }}/backups/cap-parameter-ext-connection.md %} - {% include {{ page.version.version }}/backups/locality-aware-access.md %} +Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup-options.md %}) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. + You can restore the backup by running: {% include_cached copy-clipboard.html %} From 9f4ced953734617e66384ee34dda29306e7f0fa4 Mon Sep 17 00:00:00 2001 From: Peach Leach Date: Tue, 31 Mar 2026 16:34:35 -0400 Subject: [PATCH 2/7] Port STRICT flag docs to v26.2 Added info on the STRICT flag to v26.2 documentation. Co-Authored-By: roachdev-claude --- src/current/_includes/v26.2/backups/backup-options.md | 3 ++- src/current/v26.2/take-and-restore-locality-aware-backups.md | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/src/current/_includes/v26.2/backups/backup-options.md b/src/current/_includes/v26.2/backups/backup-options.md index a4c3eeae595..c42a7366e79 100644 --- a/src/current/_includes/v26.2/backups/backup-options.md +++ b/src/current/_includes/v26.2/backups/backup-options.md @@ -5,4 +5,5 @@ `detached` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | When a backup runs in `detached` mode, it will execute asynchronously. The job ID will be returned after the backup [job creation]({% link {{ page.version.version }}/backup-architecture.md %}#job-creation-phase) completes. Note that with `detached` specified, further job information and the job completion status will not be returned. For more on the differences between the returned job data, see the [example]({% link {{ page.version.version }}/backup.md %}#run-a-backup-asynchronously). To check on the job status, use the [`SHOW JOBS`](show-jobs.html) statement. Backups running on a [schedule](create-schedule-for-backup.html) have the `detached` option applied implicitly.

To run a backup within a [transaction](transactions.html), use the `detached` option. `EXECUTION LOCALITY` | Key-value pairs | Restricts the execution of the backup to nodes that match the defined locality filter requirements. For example, `WITH EXECUTION LOCALITY = 'region=us-west-1a,cloud=aws'`.

Refer to [Take Locality-restricted backups]({% link {{ page.version.version }}/take-locality-restricted-backups.md %}) for usage and reference detail. `kms` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | The URI of the cryptographic key stored in a key management service (KMS), or a comma-separated list of key URIs, used to [take and restore encrypted backups]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples). Refer to [URI Formats]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#uri-formats). The key or keys are used to encrypt the manifest and data files that the `BACKUP` statement generates and to decrypt them during a [restore]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples) operation, and to list the contents of the backup when using [`SHOW BACKUP`]({% link {{ page.version.version }}/show-backup.md %}).

AWS KMS, Google Cloud KMS, and Azure Key Vault are supported. -`incremental_location` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | Create an incremental backup in a different location than the default incremental backup location.

`WITH incremental_location = 'explicit_incrementals_URI'`

See [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations) for usage. \ No newline at end of file +`incremental_location` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | Create an incremental backup in a different location than the default incremental backup location.

`WITH incremental_location = 'explicit_incrementals_URI'`

See [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations) for usage. +`STRICT` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | A backup that runs in `STRICT` mode fails if it attempts to back up data from a key-value node with a particular locality tag to a bucket with a different locality tag. \ No newline at end of file diff --git a/src/current/v26.2/take-and-restore-locality-aware-backups.md b/src/current/v26.2/take-and-restore-locality-aware-backups.md index c86e24b057e..ddccd25baa9 100644 --- a/src/current/v26.2/take-and-restore-locality-aware-backups.md +++ b/src/current/v26.2/take-and-restore-locality-aware-backups.md @@ -45,6 +45,8 @@ When you run the `BACKUP` statement for a locality-aware backup, check the follo - {% include {{ page.version.version }}/backups/cap-parameter-ext-connection.md %} - {% include {{ page.version.version }}/backups/locality-aware-access.md %} +Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup-options.md %}) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. + You can restore the backup by running: {% include_cached copy-clipboard.html %} From 94501aade7ae3e734afd8980945f17a40c310811 Mon Sep 17 00:00:00 2001 From: Peach Leach Date: Thu, 2 Apr 2026 13:59:51 -0400 Subject: [PATCH 3/7] Added known issue for restore (26.2 only) --- src/current/_includes/v26.2/known-limitations/restore-zones.md | 1 + src/current/v26.2/restore.md | 1 + 2 files changed, 2 insertions(+) create mode 100644 src/current/_includes/v26.2/known-limitations/restore-zones.md diff --git a/src/current/_includes/v26.2/known-limitations/restore-zones.md b/src/current/_includes/v26.2/known-limitations/restore-zones.md new file mode 100644 index 00000000000..f2b5ab94c5e --- /dev/null +++ b/src/current/_includes/v26.2/known-limitations/restore-zones.md @@ -0,0 +1 @@ +When restoring from [non-cluster backups]({% link {{ page.version.version }}/backup.md %}#back-up-a-database), `RESTORE` does not restore [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) for restored objects. [#159929](https://github.com/cockroachdb/cockroach/issues/159929) \ No newline at end of file diff --git a/src/current/v26.2/restore.md b/src/current/v26.2/restore.md index 32943361078..07fc051afc1 100644 --- a/src/current/v26.2/restore.md +++ b/src/current/v26.2/restore.md @@ -584,6 +584,7 @@ For more detail on using this option with `BACKUP`, see [Incremental backups wit - {% include {{ page.version.version }}/known-limitations/restore-udf.md %} - {% include {{ page.version.version }}/known-limitations/restore-tables-non-multi-reg.md %} +- {% include {{ page.version.version }}/known-limitations/restore-zones.md %} - {% include {{ page.version.version }}/known-limitations/restore-multiregion-match.md %} ## See also From 1b3c7c5af57759fca21fa01040bb538b84ae7335 Mon Sep 17 00:00:00 2001 From: Peach Leach Date: Thu, 2 Apr 2026 14:44:43 -0400 Subject: [PATCH 4/7] broken link --- src/current/v26.1/take-and-restore-locality-aware-backups.md | 2 +- src/current/v26.2/take-and-restore-locality-aware-backups.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/current/v26.1/take-and-restore-locality-aware-backups.md b/src/current/v26.1/take-and-restore-locality-aware-backups.md index ddccd25baa9..d0ac7aa0ae0 100644 --- a/src/current/v26.1/take-and-restore-locality-aware-backups.md +++ b/src/current/v26.1/take-and-restore-locality-aware-backups.md @@ -45,7 +45,7 @@ When you run the `BACKUP` statement for a locality-aware backup, check the follo - {% include {{ page.version.version }}/backups/cap-parameter-ext-connection.md %} - {% include {{ page.version.version }}/backups/locality-aware-access.md %} -Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup-options.md %}) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. +Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup.md %}#options) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. You can restore the backup by running: diff --git a/src/current/v26.2/take-and-restore-locality-aware-backups.md b/src/current/v26.2/take-and-restore-locality-aware-backups.md index ddccd25baa9..d0ac7aa0ae0 100644 --- a/src/current/v26.2/take-and-restore-locality-aware-backups.md +++ b/src/current/v26.2/take-and-restore-locality-aware-backups.md @@ -45,7 +45,7 @@ When you run the `BACKUP` statement for a locality-aware backup, check the follo - {% include {{ page.version.version }}/backups/cap-parameter-ext-connection.md %} - {% include {{ page.version.version }}/backups/locality-aware-access.md %} -Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup-options.md %}) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. +Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup.md %}#options) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. You can restore the backup by running: From 2c0a6ef73a7cb489666b0b00066a7c546a681c35 Mon Sep 17 00:00:00 2001 From: Peach Leach Date: Tue, 7 Apr 2026 16:00:26 -0400 Subject: [PATCH 5/7] changed known limitation issue --- src/current/_includes/v26.2/known-limitations/restore-zones.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_includes/v26.2/known-limitations/restore-zones.md b/src/current/_includes/v26.2/known-limitations/restore-zones.md index f2b5ab94c5e..4dfad262e73 100644 --- a/src/current/_includes/v26.2/known-limitations/restore-zones.md +++ b/src/current/_includes/v26.2/known-limitations/restore-zones.md @@ -1 +1 @@ -When restoring from [non-cluster backups]({% link {{ page.version.version }}/backup.md %}#back-up-a-database), `RESTORE` does not restore [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) for restored objects. [#159929](https://github.com/cockroachdb/cockroach/issues/159929) \ No newline at end of file +When restoring from [non-cluster backups]({% link {{ page.version.version }}/backup.md %}#back-up-a-database), `RESTORE` does not restore [zone configurations]({% link {{ page.version.version }}/configure-replication-zones.md %}) for restored objects. [#167824](https://github.com/cockroachdb/cockroach/issues/167824) \ No newline at end of file From e65d4c519a33d8a9a1859f4dccd9390f7811b683 Mon Sep 17 00:00:00 2001 From: Peach Leach Date: Thu, 9 Apr 2026 16:10:24 -0400 Subject: [PATCH 6/7] changes from tech review --- src/current/_includes/v26.1/backups/backup-options.md | 2 +- src/current/_includes/v26.2/backups/backup-options.md | 2 +- src/current/v26.1/take-and-restore-locality-aware-backups.md | 2 +- src/current/v26.2/take-and-restore-locality-aware-backups.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/current/_includes/v26.1/backups/backup-options.md b/src/current/_includes/v26.1/backups/backup-options.md index c42a7366e79..049f881bc74 100644 --- a/src/current/_includes/v26.1/backups/backup-options.md +++ b/src/current/_includes/v26.1/backups/backup-options.md @@ -6,4 +6,4 @@ `EXECUTION LOCALITY` | Key-value pairs | Restricts the execution of the backup to nodes that match the defined locality filter requirements. For example, `WITH EXECUTION LOCALITY = 'region=us-west-1a,cloud=aws'`.

Refer to [Take Locality-restricted backups]({% link {{ page.version.version }}/take-locality-restricted-backups.md %}) for usage and reference detail. `kms` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | The URI of the cryptographic key stored in a key management service (KMS), or a comma-separated list of key URIs, used to [take and restore encrypted backups]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples). Refer to [URI Formats]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#uri-formats). The key or keys are used to encrypt the manifest and data files that the `BACKUP` statement generates and to decrypt them during a [restore]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples) operation, and to list the contents of the backup when using [`SHOW BACKUP`]({% link {{ page.version.version }}/show-backup.md %}).

AWS KMS, Google Cloud KMS, and Azure Key Vault are supported. `incremental_location` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | Create an incremental backup in a different location than the default incremental backup location.

`WITH incremental_location = 'explicit_incrementals_URI'`

See [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations) for usage. -`STRICT` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | A backup that runs in `STRICT` mode fails if it attempts to back up data from a key-value node with a particular locality tag to a bucket with a different locality tag. \ No newline at end of file +`STRICT` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | A locality-aware backup running in `STRICT` mode fails if it cannot back up data from a node with a locality tag to a bucket with a matching locality tag. \ No newline at end of file diff --git a/src/current/_includes/v26.2/backups/backup-options.md b/src/current/_includes/v26.2/backups/backup-options.md index c42a7366e79..049f881bc74 100644 --- a/src/current/_includes/v26.2/backups/backup-options.md +++ b/src/current/_includes/v26.2/backups/backup-options.md @@ -6,4 +6,4 @@ `EXECUTION LOCALITY` | Key-value pairs | Restricts the execution of the backup to nodes that match the defined locality filter requirements. For example, `WITH EXECUTION LOCALITY = 'region=us-west-1a,cloud=aws'`.

Refer to [Take Locality-restricted backups]({% link {{ page.version.version }}/take-locality-restricted-backups.md %}) for usage and reference detail. `kms` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | The URI of the cryptographic key stored in a key management service (KMS), or a comma-separated list of key URIs, used to [take and restore encrypted backups]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples). Refer to [URI Formats]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#uri-formats). The key or keys are used to encrypt the manifest and data files that the `BACKUP` statement generates and to decrypt them during a [restore]({% link {{ page.version.version }}/take-and-restore-encrypted-backups.md %}#examples) operation, and to list the contents of the backup when using [`SHOW BACKUP`]({% link {{ page.version.version }}/show-backup.md %}).

AWS KMS, Google Cloud KMS, and Azure Key Vault are supported. `incremental_location` | [`STRING`]({% link {{ page.version.version }}/string.md %}) | Create an incremental backup in a different location than the default incremental backup location.

`WITH incremental_location = 'explicit_incrementals_URI'`

See [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations) for usage. -`STRICT` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | A backup that runs in `STRICT` mode fails if it attempts to back up data from a key-value node with a particular locality tag to a bucket with a different locality tag. \ No newline at end of file +`STRICT` | [`BOOL`]({% link {{ page.version.version }}/bool.md %}) / None | A locality-aware backup running in `STRICT` mode fails if it cannot back up data from a node with a locality tag to a bucket with a matching locality tag. \ No newline at end of file diff --git a/src/current/v26.1/take-and-restore-locality-aware-backups.md b/src/current/v26.1/take-and-restore-locality-aware-backups.md index d0ac7aa0ae0..a34b0c1edbc 100644 --- a/src/current/v26.1/take-and-restore-locality-aware-backups.md +++ b/src/current/v26.1/take-and-restore-locality-aware-backups.md @@ -45,7 +45,7 @@ When you run the `BACKUP` statement for a locality-aware backup, check the follo - {% include {{ page.version.version }}/backups/cap-parameter-ext-connection.md %} - {% include {{ page.version.version }}/backups/locality-aware-access.md %} -Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup.md %}#options) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. +Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, edge cases exist in which a locality-aware backup may be forced to write to the default bucket instead, such as when the cluster has unhealthy nodes. Use the [`STRICT`]({% link {{ page.version.version }}/backup.md %}#options) option when creating a locality-aware backup to force the backup to fail in these cases to avoid violating data domiciling requirements. You can restore the backup by running: diff --git a/src/current/v26.2/take-and-restore-locality-aware-backups.md b/src/current/v26.2/take-and-restore-locality-aware-backups.md index d0ac7aa0ae0..a34b0c1edbc 100644 --- a/src/current/v26.2/take-and-restore-locality-aware-backups.md +++ b/src/current/v26.2/take-and-restore-locality-aware-backups.md @@ -45,7 +45,7 @@ When you run the `BACKUP` statement for a locality-aware backup, check the follo - {% include {{ page.version.version }}/backups/cap-parameter-ext-connection.md %} - {% include {{ page.version.version }}/backups/locality-aware-access.md %} -Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, in cases involving unhealthy nodes, a locality-aware backup may be forced to write to a bucket in the default region instead. Use the [`STRICT`]({% link {{ page.version.version }}/backup.md %}#options) option when creating a locality-aware backup to force the backup to fail rather than writing to a bucket in a region that does not match the data being written. +Locality-aware backups attempt to match data to buckets in corresponding regions as specified. However, edge cases exist in which a locality-aware backup may be forced to write to the default bucket instead, such as when the cluster has unhealthy nodes. Use the [`STRICT`]({% link {{ page.version.version }}/backup.md %}#options) option when creating a locality-aware backup to force the backup to fail in these cases to avoid violating data domiciling requirements. You can restore the backup by running: From 51553127c3aa7b467167efcc05e9ca9b5b01dfc0 Mon Sep 17 00:00:00 2001 From: "release-notes-automation[bot]" <195008642+release-notes-automation[bot]@users.noreply.github.com> Date: Fri, 10 Apr 2026 16:55:09 +0000 Subject: [PATCH 7/7] Release Notes for v25.4-v25.4.8 (#23176) --- src/current/_data/releases.yml | 28 +++++++++++++++++++ .../_includes/releases/v25.4/v25.4.8.md | 12 ++++++++ 2 files changed, 40 insertions(+) create mode 100644 src/current/_includes/releases/v25.4/v25.4.8.md diff --git a/src/current/_data/releases.yml b/src/current/_data/releases.yml index 59db9dd568a..ec464dfe0e9 100644 --- a/src/current/_data/releases.yml +++ b/src/current/_data/releases.yml @@ -11172,3 +11172,31 @@ docker_arm_limited_access: false source: true previous_release: v24.1.26 + + +- release_name: v25.4.8 + major_version: v25.4 + release_date: '2026-04-10' + release_type: Production + go_version: go1.25.5 + sha: 466b1cd8cd953daa0c18a38cd32466a5c3dc73a3 + 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.7 diff --git a/src/current/_includes/releases/v25.4/v25.4.8.md b/src/current/_includes/releases/v25.4/v25.4.8.md new file mode 100644 index 00000000000..4896abe0b3e --- /dev/null +++ b/src/current/_includes/releases/v25.4/v25.4.8.md @@ -0,0 +1,12 @@ +## v25.4.8 + +Release Date: April 10, 2026 + +{% include releases/new-release-downloads-docker-image.md release=include.release %} + +

Bug fixes

+ +- Fixed a bug where `IMPORT` error messages could include unredacted cloud storage credentials from the source URI. Credentials are now stripped from URIs before they appear in error messages. [#168040][#168040] + + +[#168040]: https://github.com/cockroachdb/cockroach/pull/168040