Conversation
postgis stopped refreshing the pg17 line and its 17-3.5 image sits on Debian bullseye, which left LTS on 2026-08-31 - no more security updates. Bump the db, dev and test images to 18-3.6 (PostgreSQL 18, bookworm-based). psql 18 understands the \restrict guards pg_dump emits, so the dump is now shipped verbatim without the strip-and-regzip pass. Claude-Session: https://claude.ai/code/session_0195FWjQNKqsSSeZuRyu8Lzi
Member
|
🎉 This issue has been resolved in version 20.0.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the db image (
Dockerfile.pg), dev image and test stack frompostgis/postgis:17-3.5to18-3.6. Upstream no longer refreshes the pg17 line and17-3.5is Debian bullseye, which left LTS on 31 Aug 2026 - the runtime base was EOL for security updates (and its apt rot is what broke the autobuild fixed in #1403).