Skip to content

chore(deps): update postgresql to the 2026-11-12 minors - #114

Open
pRob3 wants to merge 1 commit into
tensorchord:mainfrom
pRob3:postgres-2026-11-minors
Open

pRob3 wants to merge 1 commit into
tensorchord:mainfrom
pRob3:postgres-2026-11-minors

Conversation

@pRob3

@pRob3 pRob3 commented Nov 17, 2026

Copy link
Copy Markdown

Bumps every PostgreSQL minor in versions.yaml to the out-of-cycle release of 2026-11-12: 14.25, 15.20, 16.16, 17.12 and 18.7.

These releases carry the 2026-11-12 security fixes; for 17.x alone that is 47 CVEs, 34 of them rated high, all fixed in 17.12. The newest published images are still 17.11-1.1.1 and 18.6-1.1.1, and Renovate has not opened a PR for this release, so I made the same change by hand, in the same shape as #106.

All five base tags exist as <version>-system-bookworm on ghcr.io/cloudnative-pg/postgresql, which is the base the Dockerfile uses. I checked each one with a manifest HEAD request on 2026-11-17. The VectorChord version stays at 1.1.1.

This stays on bookworm on purpose and does not overlap #113. Moving to trixie changes glibc, which changes collation behaviour for existing clusters, so it is a different kind of change from a patch release.

🤖 Generated with Claude Code

14.25, 15.20, 16.16, 17.12 and 18.7. All five exist as <version>-system-bookworm on ghcr.io/cloudnative-pg/postgresql.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant