fix: rewire postgresVersion input in pg_upgrade publish workflows#2227
Merged
Conversation
pcnc
approved these changes
Jun 19, 2026
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
2 participants
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.
This adds #2225 to
release/17.6in order to allow us to rebuild the pg-upgrade-scripts tarball for production to include #2220 . Those are the only 2 commits that exist inrelease/17.6that differ from tag17.6.1.127and are the fixes we need.As soon as this PR is merged we'll need to terminate the 'other' Nix jobs that are triggered by pushing to
release/*, and ONLY allow https://github.com/supabase/postgres/actions/workflows/publish-nix-pgupgrade-scripts.yml to continue.This was validated via https://github.com/supabase/postgres/actions/runs/27762146904/job/82140324060 for staging and confirmed that staging is working as expected.