chore(cli): read Postgres image from Dockerfile manifest - #5649
Merged
Conversation
jgoux
marked this pull request as ready for review
June 22, 2026 12:01
Contributor
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@3d643af8a0d5f9bd7848990321a113a8c4022b17Preview package for commit |
Coly010
approved these changes
Jun 22, 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.
Summary
Make the TS legacy Postgres image resolver read the default image from the same Dockerfile manifest used by the Go config image table.
This removes the duplicated PG17 tag from the TS port, keeps
db dumpaligned with Dependabot updates toapps/cli-go/pkg/config/templates/Dockerfile, and preserves the existing service image parser export for callers.Context
PR #5083 highlighted that PG image selection can drift when the default Postgres image is copied into multiple places. The active TS
db dumppath already selected a PG17 image, but its hardcoded tag had drifted from the Dockerfile manifest.