Skip to content

fix: re-pin the PostgreSQL source tarball when Renovate bumps it - #490

Merged
cplieger merged 1 commit into
mainfrom
fix/repin-postgres
Nov 20, 2026
Merged

cplieger merged 1 commit into
mainfrom
fix/repin-postgres

Conversation

@cplieger

Copy link
Copy Markdown
Owner

Adds postgres to the dependencies whose Dockerfile sha256 pin repin-sha.sh recomputes after a bump. pg-autodump now builds its PostgreSQL client from the source release named by ARG PG_VERSION, tracked as depName=postgres with a # repin: marker on PG_SHA256 (cplieger/pg-autodump#977). Without this entry, each PostgreSQL bump opens red until someone recomputes the pin by hand.

pg-autodump builds its PostgreSQL client from the source release named by
ARG PG_VERSION (depName postgres), with a repin marker on PG_SHA256. Adding
the dep here lets repin-sha.sh recompute that pin in the bump commit.
@cplieger
cplieger merged commit f51c357 into main Nov 20, 2026
22 checks passed
@cplieger
cplieger deleted the fix/repin-postgres branch November 20, 2026 12:11
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