Repository navigation
fix(postgres): support PostgreSQL 18 defaults with compatible volume paths - #54
Merged
kaanyagci merged 7 commits intoOct 11, 2026
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/postgres-18.x
branch
from
October 8, 2026 03:12
73d5afc to
70ec239
Compare
renovate
Bot
force-pushed
the
renovate/postgres-18.x
branch
from
October 8, 2026 03:15
70ec239 to
b06086b
Compare
kaanyagci
marked this pull request as draft
October 8, 2026 04:00
kaanyagci
changed the base branch from
main
to
renovate/major-github-artifact-actions
October 8, 2026 04:11
kaanyagci
added this pull request to stack #55
October 8, 2026 04:11
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
kaanyagci
marked this pull request as ready for review
October 11, 2026 10:22
* Update actions/upload-artifact action to v7 * fix(ci): preserve ZIP evidence contract for artifact action v7 --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Kaan Yagci <kaan.yagci@makepad.fr>
An error occurred while trying to automatically change base from
renovate/major-github-artifact-actions
to
main
October 11, 2026 15:23
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.
The PostgreSQL 18 default now uses an explicit PGDATA matching the existing volume mount. Without it, a fresh PostgreSQL 18 container rejects the old mount layout. Existing production and canary environments remain pinned to their current PostgreSQL 16 images; upgrading their data requires the separately documented backup/restore cutover and explicit pin change.
Added an isolated real-container compatibility test: create PostgreSQL 16 data, restore its logical backup into a fresh PostgreSQL 18 volume, verify rows and values, reject direct reuse of the PostgreSQL 16 volume by PostgreSQL 18, then restart PostgreSQL 16 and verify its original data remains intact. Configuration validation enforces the mount/PGDATA contract.
Validation: the new test reproduced the original startup failure, passed after the fix, and the complete scripts/run-ci.sh suite passed on an isolated Linux Docker daemon. No production database migration or deployment was performed.