Repository navigation
chore(postgres): use stable PostgreSQL 18.6 in development and CI - #2413
Merged
Merged
Conversation
Co-authored-by: Codex <codex@delicious233.com>
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the
|
Co-authored-by: Codex <codex@delicious233.com>
DeliciousBuding
force-pushed
the
chore/pg18-stable
branch
from
October 30, 2026 09:33
0283e47 to
7d9154d
Compare
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
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.
Summary
Use the verified current stable PostgreSQL 18.6 in development, CI and fixture E2E.
Official version source: https://www.postgresql.org/support/versioning/ and https://www.postgresql.org/versions.json
Compatibility and migration boundary
A major-version image swap is not a database migration. Existing PG16 data needs a verified dump/restore or pg_upgrade with backup, stop-write and cutover checks. The old data volume remains available; this PR does not migrate or overwrite an external live database.
Verification
Pending