switch to pg 18.3-alpine

Author: krisztianfekete

DEVELOPMENT.md

@@ -37,7 +37,7 @@ Standard development uses `dev-backend` + `dev-frontend` in separate terminals.
 The default in-memory backend keeps `make dev-backend` zero-config. To exercise the async run pipeline locally, bring up a Postgres alongside the app:
 
 ```bash
-make pg-up             # start postgres:17-alpine in a docker container (port 5432, ephemeral via --rm)
+make pg-up             # start postgres:18.3-alpine in a docker container (port 5432, ephemeral via --rm)
 make migrate           # apply the agentevals schema
 make dev-backend-pg    # pg-up + migrate + serve --dev with backend=postgres wired up
 make pg-down           # stop the container; data is discarded with --rm

Makefile

@@ -66,7 +66,7 @@ pg-up:
 			-e POSTGRES_USER=$(PG_USER) \
 			-e POSTGRES_PASSWORD=$(PG_PASSWORD) \
 			-e POSTGRES_DB=$(PG_DATABASE) \
-			-p $(PG_PORT):5432 postgres:17-alpine; \
+			-p $(PG_PORT):5432 postgres:18.3-alpine; \
 	else \
 		echo "container $(PG_CONTAINER) already running"; \
 	fi

charts/agentevals/values.yaml

@@ -210,7 +210,7 @@ database:
         # -- Bundled Postgres image name
         name: postgres
         # -- Bundled Postgres image tag
-        tag: "17"
+        tag: "18.3-alpine"
         # -- Bundled Postgres image pull policy
         pullPolicy: IfNotPresent
       # -- PersistentVolumeClaim size for the bundled Postgres data