feat: update default PostgreSQL version to 18.3-system-trixie

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: postgres-versions-updater

.github/pg_versions.json

@@ -1,23 +1,23 @@
 {
   "18": [
-    "18.1-system-trixie",
-    "18.0-system-trixie"
+    "18.3-system-trixie",
+    "18.2-system-trixie"
   ],
   "17": [
-    "17.7-system-trixie",
-    "17.6-system-trixie"
+    "17.9-system-trixie",
+    "17.8-system-trixie"
   ],
   "16": [
-    "16.11-system-trixie",
-    "16.10-system-trixie"
+    "16.13-system-trixie",
+    "16.12-system-trixie"
   ],
   "15": [
-    "15.15-system-trixie",
-    "15.14-system-trixie"
+    "15.17-system-trixie",
+    "15.16-system-trixie"
   ],
   "14": [
-    "14.20-system-trixie",
-    "14.19-system-trixie"
+    "14.22-system-trixie",
+    "14.21-system-trixie"
   ],
   "13": [
     "13.22-system-trixie",

docs/src/bootstrap.md

@@ -614,7 +614,7 @@ file on the source PostgreSQL instance:
 host replication streaming_replica all md5
 ```
 
-The following manifest creates a new PostgreSQL 18.1 cluster,
+The following manifest creates a new PostgreSQL 18.3 cluster,
 called `target-db`, using the `pg_basebackup` bootstrap method
 to clone an external PostgreSQL cluster defined as `source-db`
 (in the `externalClusters` array). As you can see, the `source-db`
@@ -629,7 +629,7 @@ metadata:
   name: target-db
 spec:
   instances: 3
-  imageName: ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie
+  imageName: ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie
 
   bootstrap:
     pg_basebackup:
@@ -649,7 +649,7 @@ spec:
 ```
 
 All the requirements must be met for the clone operation to work, including
-the same PostgreSQL version (in our case 18.1).
+the same PostgreSQL version (in our case 18.3).
 
 #### TLS certificate authentication
 
@@ -665,7 +665,7 @@ in the same Kubernetes cluster.
     outside the Kubernetes cluster.
 :::
 
-The manifest defines a new PostgreSQL 18.1 cluster called `cluster-clone-tls`,
+The manifest defines a new PostgreSQL 18.3 cluster called `cluster-clone-tls`,
 which is bootstrapped using the `pg_basebackup` method from the `cluster-example`
 external cluster. The host is identified by the read/write service
 in the same cluster, while the `streaming_replica` user is authenticated
@@ -680,7 +680,7 @@ metadata:
   name: cluster-clone-tls
 spec:
   instances: 3
-  imageName: ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie
+  imageName: ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie
 
   bootstrap:
     pg_basebackup:

docs/src/declarative_hibernation.md

@@ -57,7 +57,7 @@ $ kubectl cnpg status <cluster-name>
 Cluster Summary
 Name:              cluster-example
 Namespace:         default
-PostgreSQL Image:  ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie
+PostgreSQL Image:  ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie
 Primary instance:  cluster-example-2
 Status:            Cluster in healthy state 
 Instances:         3

docs/src/image_catalog.md

@@ -44,7 +44,7 @@ spec:
     - major: 17
       image: ghcr.io/cloudnative-pg/postgresql:17.6-system-trixie
     - major: 18
-      image: ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie
+      image: ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie
 ```
 
 **Example of a Cluster-Wide Catalog using `ClusterImageCatalog` Resource:**
@@ -63,7 +63,7 @@ spec:
     - major: 17
       image: ghcr.io/cloudnative-pg/postgresql:17.6-system-trixie
     - major: 18
-      image: ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie
+      image: ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie
 ```
 
 A `Cluster` resource has the flexibility to reference either an `ImageCatalog`

docs/src/index.md

@@ -99,7 +99,7 @@ Three image flavors are available, each extending the previous one:
     Barman Cloud plugin, or another supported backup solution.
 :::
 
-By default, this version of CloudNativePG deploys `ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie`.
+By default, this version of CloudNativePG deploys `ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie`.
 
 All images are signed and shipped with SBOM and provenance attestations.
 Weekly automated builds ensure that critical vulnerabilities (CVEs) are promptly fixed.

docs/src/kubectl-plugin.md

@@ -1078,7 +1078,7 @@ it from the actual pod. This means that you will be using the `postgres` user.
 ```console
 $ kubectl cnpg psql cluster-example
 
-psql (18.1 (Debian 18.1-1.pgdg110+1))
+psql (18.3 (Debian 18.3-1.pgdg110+1))
 Type "help" for help.
 
 postgres=#
@@ -1090,7 +1090,7 @@ select to work against a replica by using the `--replica` option:
 ```console
 $ kubectl cnpg psql --replica cluster-example
 
-psql (18.1 (Debian 18.1-1.pgdg110+1))
+psql (18.3 (Debian 18.3-1.pgdg110+1))
 
 Type "help" for help.
 

docs/src/monitoring.md

@@ -258,7 +258,7 @@ cnpg_collector_up{cluster="cluster-example"} 1
 
 # HELP cnpg_collector_postgres_version Postgres version
 # TYPE cnpg_collector_postgres_version gauge
-cnpg_collector_postgres_version{cluster="cluster-example",full="18.1"} 18.1
+cnpg_collector_postgres_version{cluster="cluster-example",full="18.3"} 18.3
 
 # HELP cnpg_collector_last_failed_backup_timestamp The last failed backup as a unix timestamp (Deprecated)
 # TYPE cnpg_collector_last_failed_backup_timestamp gauge

docs/src/postgis.md

@@ -70,7 +70,7 @@ kind: Cluster
 metadata:
   name: cluster-postgis
 spec:
-  imageName: ghcr.io/cloudnative-pg/postgresql:18.1-minimal-trixie
+  imageName: ghcr.io/cloudnative-pg/postgresql:18.3-minimal-trixie
   instances: 1
 
   storage:
@@ -112,7 +112,7 @@ metadata:
   name: cluster-postgis
 spec:
   instances: 1
-  imageName: ghcr.io/cloudnative-pg/postgis:18.1-3.6.2-system-trixie
+  imageName: ghcr.io/cloudnative-pg/postgis:18.3-3.6.2-system-trixie
   storage:
     size: 1Gi
 ```

docs/src/samples/cluster-example-full.yaml

@@ -35,7 +35,7 @@ metadata:
   name: cluster-example-full
 spec:
   description: "Example of cluster"
-  imageName: ghcr.io/cloudnative-pg/postgresql:18.1-system-trixie
+  imageName: ghcr.io/cloudnative-pg/postgresql:18.3-system-trixie
   # imagePullSecret is only required if the images are located in a private registry
   # imagePullSecrets:
   #   - name: private_registry_access

docs/src/samples/postgis-example.yaml

@@ -3,7 +3,7 @@ kind: Cluster
 metadata:
   name: postgis-example
 spec:
-  imageName: ghcr.io/cloudnative-pg/postgresql:18.1-minimal-trixie
+  imageName: ghcr.io/cloudnative-pg/postgresql:18.3-minimal-trixie
   instances: 1
 
   storage: