Run local and test services on PostgreSQL 18.6 - #17
Merged
Merged
Conversation
Neon runs 18.6 in production and previews, so the tests now run on the same major version. The 18 image stores data under /var/lib/postgresql/18/docker and refuses a volume that holds a 17 cluster, so the volume is renamed and an existing checkout starts a fresh development database. Full suite (175 tests), db:verify and packages:verify pass on 18.6. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
1 participant
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.
Runs pgstencil's local and test services on PostgreSQL 18.6, to match Neon in production and previews.
compose.yamlusespostgres:18.6-alpine(the tag exists on Docker Hub, and Neon reports 18.6).postgres-data→postgres-18-dataand mounted at/var/lib/postgresql. The 18 image keeps its data under/var/lib/postgresql/18/dockerand refuses a volume that holds a 17 cluster. I checked both mount paths against a real 17 volume, and both exit with the entrypoint's error. With the rename, an existing checkout starts a fresh development database instead of failing, and the old volume stays until removed. The README says so.Verified on 18.6:
db:verify,typecheck,format:check, the full suite (21 files, 175 tests, Docker), andpackages:verifyon the committed tree. The Better Auth schema-plan test and the OAuth suites pass unchanged.The compose file ships inside the
pgstencilpackage, so a consumer that re-vendors picks up 18 for its own test database. Dormouse's production backup and restore check are moved to 18.6 in a separate PR there. TTR's production stays on 17 until its database is recreated.🤖 Generated with Claude Code