fix(docker): bump supabase/postgres from 17.6.1.165 to 17.6.1.166 in /apps/cli-go/pkg/config/templates - #6369
Conversation
Bumps supabase/postgres from 17.6.1.165 to 17.6.1.166. --- updated-dependencies: - dependency-name: supabase/postgres dependency-version: 17.6.1.166 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3ef070a91e
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| @@ -1,5 +1,5 @@ | |||
| # Exposed for updates by .github/dependabot.yml | |||
| FROM supabase/postgres:17.6.1.165 AS pg | |||
| FROM supabase/postgres:17.6.1.166 AS pg | |||
There was a problem hiding this comment.
Sync the stack catalog with the PostgreSQL bump
When the TypeScript stack starts an unlinked project or otherwise has no PostgreSQL version override, fillServiceVersionManifest and StackConfigResolver still select packages/stack/src/ServiceCatalog.ts:131, which remains 17.6.1.165. This change therefore upgrades only the embedded Go Docker manifest while the main stack runtime continues pulling the old image, and packages/stack/scripts/sync-versions-from-dockerfile.ts --check reports the manifests as out of sync; update the catalog to 17.6.1.166 as part of this bump.
Useful? React with 👍 / 👎.
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@fbbf20ea7acd0743634d81822eb7dd012178bd0cPreview package for commit |
Bumps supabase/postgres from 17.6.1.165 to 17.6.1.166.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)