Repository navigation
fix: re-pin the PostgreSQL source tarball when Renovate bumps it - #490
Merged
Merged
Conversation
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.
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.
Adds
postgresto the dependencies whose Dockerfile sha256 pinrepin-sha.shrecomputes after a bump. pg-autodump now builds its PostgreSQL client from the source release named byARG PG_VERSION, tracked asdepName=postgreswith a# repin:marker onPG_SHA256(cplieger/pg-autodump#977). Without this entry, each PostgreSQL bump opens red until someone recomputes the pin by hand.