Skip to content

chore(deps): keep PostgreSQL majors out of the update stream - #995

Merged
MBombeck merged 1 commit into
mainfrom
chore/postgres-major-ignore
Sep 16, 2026
Merged

MBombeck merged 1 commit into
mainfrom
chore/postgres-major-ignore

Conversation

@MBombeck

Copy link
Copy Markdown
Owner

The docker-compose ecosystem added in #988 proposed postgres 16.15 to 18.6 on its first run (#989). A PostgreSQL major changes the on-disk format, so that is a migration (pg_upgrade or dump and restore), not an update to merge.

Adds an ignore rule for major updates of the database image and a guard case that fails if it is dropped. Minor releases keep arriving as PRs.

The compose ecosystem added last change did its job on the first run and
immediately proposed 16.15 to 18.6. A PostgreSQL major changes the
on-disk format, so merging that would hand self-hosters a container that
cannot read their data directory without pg_upgrade or a dump and
restore. Minor releases keep arriving as reviewable PRs; a major is a
project decision with a migration path behind it, not a weekly bump.

The guard grows a case for the ignore rule, so dropping it fails rather
than quietly re-opening the door.
@MBombeck
MBombeck merged commit 01cc719 into main Sep 16, 2026
24 checks passed
@MBombeck
MBombeck deleted the chore/postgres-major-ignore branch September 16, 2026 11:46
@MBombeck MBombeck mentioned this pull request Sep 16, 2026
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