Ship PostgreSQL 17.11 image (PGDG 2026-08-13, CVE-2026-14664)

[Stanleyvertus]

PGDG released PostgreSQL 17.11 on 2026-08-13 (release notes), including CVE-2026-14664.

Hosted Supabase still has no 17.11 engine:

• GET /v1/projects/{ref}/upgrade/eligibility → target_upgrade_versions only postgres_version: "17" with images supabase-postgres-17.6.1.155 (ga) / 17.6.1.164 (preview).
• POST /v1/projects/{ref}/upgrade { "target_version": "17.11" } → 400 Invalid database engine selected: 17.11.
• This repo develop ansible/vars.yml: postgres17: "17.6.1.165".
• Docker Hub supabase/postgres tags?name=17.11 → count: 0.
• SELECT version() on hosted 17 projects still reports 17.6.

Request: publish a supabase/postgres 17.11 image and expose it on the hosted upgrade eligibility list (so target_version can be 17.11, or an app_version that contains 17.11). A 17.6.1.x bump is not a substitute for the PGDG 17.11 fix.

Happy to re-test the moment a 17.11 target appears.

[nthtrung09it]

Waiting for that too.
About a year and the postgres 18 is still not supported too.