fix(docker): bump postgrest/postgrest from v14.16 to v16.0 in /apps/cli-go/pkg/config/templates - #6134
Conversation
Bumps postgrest/postgrest from v14.16 to v16.0. --- updated-dependencies: - dependency-name: postgrest/postgrest dependency-version: v16.0 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@fdd8ec9d190713ee8277fd8b7cf88054e1eaded4Preview package for commit |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fdd8ec9d19
ℹ️ 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".
| FROM library/kong:2.8.1 AS kong | ||
| FROM axllent/mailpit:v1.30.2 AS mailpit | ||
| FROM postgrest/postgrest:v14.16 AS postgrest | ||
| FROM postgrest/postgrest:v16.0 AS postgrest |
There was a problem hiding this comment.
Sync the stack default PostgREST version
This bump updates the Dockerfile manifest that legacy start/services reads, but @supabase/stack still has postgrest defaultVersion: "14.16" in packages/stack/src/ServiceCatalog.ts; the next/v3 start path fills omitted postgrest.version from DEFAULT_VERSIONS, so it will keep launching/downloading v14.16 while the Dockerfile-backed CLI paths report/use v16.0. Please run the stack version sync script or update the catalog in the same change so both stack implementations use the same PostgREST baseline.
Useful? React with 👍 / 👎.
| FROM library/kong:2.8.1 AS kong | ||
| FROM axllent/mailpit:v1.30.2 AS mailpit | ||
| FROM postgrest/postgrest:v14.16 AS postgrest | ||
| FROM postgrest/postgrest:v16.0 AS postgrest |
There was a problem hiding this comment.
Reject schemas that v16 refuses to start with
With this default image, any local project that has api.schemas (or SUPABASE_API_SCHEMAS) including pg_catalog or information_schema will now create PostgREST v16 with those values passed straight through as PGRST_DB_SCHEMAS, and the v16 migration notes say PostgREST fails at startup for exactly those schemas. Since the config schema/start path still accepts them, existing projects using either schema now fail during supabase start health checks; add a preflight validation/error or avoid the v16 default until this incompatibility is handled.
Useful? React with 👍 / 👎.
| FROM library/kong:2.8.1 AS kong | ||
| FROM axllent/mailpit:v1.30.2 AS mailpit | ||
| FROM postgrest/postgrest:v14.16 AS postgrest | ||
| FROM postgrest/postgrest:v16.0 AS postgrest |
There was a problem hiding this comment.
Sync the stack default PostGREST version
This bump updates the Dockerfile manifest that legacy start/services reads, but @supabase/stack still has postgrest defaultVersion: "14.16" in packages/stack/src/ServiceCatalog.ts; the next/v3 start path fills omitted postgrest.version from DEFAULT_VERSIONS, so it will keep launching/downloading v14.16 while the Dockerfile-backed CLI paths report/use v16.0. Please run the stack version sync script or update the catalog in the same change so both stack implementations use the same PostgREST baseline.
Useful? React with 👍 / 👎.
Bumps postgrest/postgrest from v14.16 to v16.0.
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)