diff --git a/website/docs/release_notes/v1.27.md b/website/docs/release_notes/v1.27.md index d691936..b21a0e8 100644 --- a/website/docs/release_notes/v1.27.md +++ b/website/docs/release_notes/v1.27.md @@ -24,15 +24,15 @@ on the release branch in GitHub. requiring explicit storage account keys or SAS tokens. ([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) -- Added support for PostgreSQL extension names containing underscores (e.g., - `pg_ivm`, `pg_stat_statements`). Extension names with underscores are +### Fixes + +- Fixed validation of PostgreSQL extension names containing underscores (e.g., + `pg_partman`, `pg_ivm`). Extension names with underscores are automatically sanitized to use hyphens for Kubernetes volume names while preserving the original name in mount paths. Webhook validation prevents naming conflicts after sanitization. Contributed by @shusaan. ([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) -### Fixes - - Fixed a critical issue where the `TimelineID` in the cluster status was not reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt diff --git a/website/docs/release_notes/v1.28.md b/website/docs/release_notes/v1.28.md index fd2cbe4..0e8758d 100644 --- a/website/docs/release_notes/v1.28.md +++ b/website/docs/release_notes/v1.28.md @@ -44,15 +44,15 @@ on the release branch in GitHub. requiring explicit storage account keys or SAS tokens. ([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) -- Added support for PostgreSQL extension names containing underscores (e.g., - `pg_ivm`, `pg_stat_statements`). Extension names with underscores are +### Fixes + +- Fixed validation of PostgreSQL extension names containing underscores (e.g., + `pg_partman`, `pg_ivm`). Extension names with underscores are automatically sanitized to use hyphens for Kubernetes volume names while preserving the original name in mount paths. Webhook validation prevents naming conflicts after sanitization. Contributed by @shusaan. ([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) -### Fixes - - Fixed a critical issue where the `TimelineID` in the cluster status was not reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt diff --git a/website/versioned_docs/version-1.27/release_notes/v1.27.md b/website/versioned_docs/version-1.27/release_notes/v1.27.md index d691936..b21a0e8 100644 --- a/website/versioned_docs/version-1.27/release_notes/v1.27.md +++ b/website/versioned_docs/version-1.27/release_notes/v1.27.md @@ -24,15 +24,15 @@ on the release branch in GitHub. requiring explicit storage account keys or SAS tokens. ([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) -- Added support for PostgreSQL extension names containing underscores (e.g., - `pg_ivm`, `pg_stat_statements`). Extension names with underscores are +### Fixes + +- Fixed validation of PostgreSQL extension names containing underscores (e.g., + `pg_partman`, `pg_ivm`). Extension names with underscores are automatically sanitized to use hyphens for Kubernetes volume names while preserving the original name in mount paths. Webhook validation prevents naming conflicts after sanitization. Contributed by @shusaan. ([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) -### Fixes - - Fixed a critical issue where the `TimelineID` in the cluster status was not reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt diff --git a/website/versioned_docs/version-1.28/release_notes/v1.27.md b/website/versioned_docs/version-1.28/release_notes/v1.27.md index d691936..b21a0e8 100644 --- a/website/versioned_docs/version-1.28/release_notes/v1.27.md +++ b/website/versioned_docs/version-1.28/release_notes/v1.27.md @@ -24,15 +24,15 @@ on the release branch in GitHub. requiring explicit storage account keys or SAS tokens. ([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) -- Added support for PostgreSQL extension names containing underscores (e.g., - `pg_ivm`, `pg_stat_statements`). Extension names with underscores are +### Fixes + +- Fixed validation of PostgreSQL extension names containing underscores (e.g., + `pg_partman`, `pg_ivm`). Extension names with underscores are automatically sanitized to use hyphens for Kubernetes volume names while preserving the original name in mount paths. Webhook validation prevents naming conflicts after sanitization. Contributed by @shusaan. ([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) -### Fixes - - Fixed a critical issue where the `TimelineID` in the cluster status was not reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt diff --git a/website/versioned_docs/version-1.28/release_notes/v1.28.md b/website/versioned_docs/version-1.28/release_notes/v1.28.md index fd2cbe4..0e8758d 100644 --- a/website/versioned_docs/version-1.28/release_notes/v1.28.md +++ b/website/versioned_docs/version-1.28/release_notes/v1.28.md @@ -44,15 +44,15 @@ on the release branch in GitHub. requiring explicit storage account keys or SAS tokens. ([#9468](https://github.com/cloudnative-pg/cloudnative-pg/pull/9468)) -- Added support for PostgreSQL extension names containing underscores (e.g., - `pg_ivm`, `pg_stat_statements`). Extension names with underscores are +### Fixes + +- Fixed validation of PostgreSQL extension names containing underscores (e.g., + `pg_partman`, `pg_ivm`). Extension names with underscores are automatically sanitized to use hyphens for Kubernetes volume names while preserving the original name in mount paths. Webhook validation prevents naming conflicts after sanitization. Contributed by @shusaan. ([#9386](https://github.com/cloudnative-pg/cloudnative-pg/pull/9386)) -### Fixes - - Fixed a critical issue where the `TimelineID` in the cluster status was not reset to 1 after a major version upgrade. Because `pg_upgrade` initializes a new timeline, keeping the old ID (e.g., timeline 2) caused replicas to attempt