fix(docker): bump the docker-minor group across 1 directory with 5 updates#5924
Conversation
…dates Bumps the docker-minor group with 5 updates in the /apps/cli-go/pkg/config/templates directory: | Package | From | To | | --- | --- | --- | | supabase/studio | `2026.07.13-sha-b5ada96` | `2026.07.20-sha-74a0848` | | supabase/gotrue | `v2.193.0` | `v2.193.1` | | supabase/realtime | `v2.113.4` | `v2.118.0` | | supabase/storage-api | `v1.66.4` | `v1.67.13` | | supabase/logflare | `1.47.1` | `1.47.2` | Updates `supabase/studio` from 2026.07.13-sha-b5ada96 to 2026.07.20-sha-74a0848 Updates `supabase/gotrue` from v2.193.0 to v2.193.1 Updates `supabase/realtime` from v2.113.4 to v2.118.0 Updates `supabase/storage-api` from v1.66.4 to v1.67.13 Updates `supabase/logflare` from 1.47.1 to 1.47.2 --- updated-dependencies: - dependency-name: supabase/studio dependency-version: 2026.07.20-sha-74a0848 dependency-type: direct:production dependency-group: docker-minor - dependency-name: supabase/gotrue dependency-version: v2.193.1 dependency-type: direct:production dependency-group: docker-minor - dependency-name: supabase/realtime dependency-version: v2.118.0 dependency-type: direct:production dependency-group: docker-minor - dependency-name: supabase/storage-api dependency-version: v1.67.13 dependency-type: direct:production dependency-group: docker-minor - dependency-name: supabase/logflare dependency-version: 1.47.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: docker-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![supabase-cli-releaser[bot]](https://avatars.githubusercontent.com/u/54469796?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 878fb8f27f
ℹ️ 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 supabase/gotrue:v2.193.1 AS gotrue | ||
| FROM supabase/realtime:v2.118.0 AS realtime | ||
| FROM supabase/storage-api:v1.67.13 AS storage | ||
| FROM supabase/logflare:1.47.2 AS logflare |
There was a problem hiding this comment.
When these Dockerfile service tags are bumped, the TypeScript stack defaults need to be regenerated as well: packages/stack/scripts/sync-versions-from-dockerfile.ts reads this manifest and rewrites packages/stack/src/versions.ts, but that file still pins the old auth/realtime/storage/studio/analytics versions. As a result the TS local stack paths that use DEFAULT_VERSIONS keep running and reporting the previous images even though this change updates the Dockerfile manifest; please run the sync script and include the generated packages/stack/src/versions.ts changes.
Useful? React with 👍 / 👎.
| FROM supabase/gotrue:v2.193.1 AS gotrue | ||
| FROM supabase/realtime:v2.118.0 AS realtime | ||
| FROM supabase/storage-api:v1.67.13 AS storage | ||
| FROM supabase/logflare:1.47.2 AS logflare |
There was a problem hiding this comment.
With this bump, the Start job in .github/workflows/cli-go-ci.yml runs ./main start with SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io, and GetRegistryImageUrls uses only that single overridden candidate. I checked the current GHCR package versions and ghcr.io/supabase/logflare:1.47.2 is not published there yet, so PR/develop CI and any users with the GHCR registry override will fail pulling the analytics image; keep the previous tag or mirror 1.47.2 before pinning it here.
Useful? React with 👍 / 👎.
| FROM postgrest/postgrest:v14.15 AS postgrest | ||
| FROM supabase/postgres-meta:v0.96.6 AS pgmeta | ||
| FROM supabase/studio:2026.07.13-sha-b5ada96 AS studio | ||
| FROM supabase/studio:2026.07.20-sha-74a0848 AS studio |
There was a problem hiding this comment.
The same GHCR-only Start path also pulls Studio, but the current GHCR Studio package does not have 2026.07.20-sha-74a0848 even though this Docker Hub tag exists. Since the registry override disables the normal Docker Hub fallback, PR/develop CI and users running with SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io will fail when supabase start tries to pull Studio; mirror this tag before pinning it or keep the previous mirrored tag.
Useful? React with 👍 / 👎.
| FROM supabase/logflare:1.47.1 AS logflare | ||
| FROM supabase/gotrue:v2.193.1 AS gotrue | ||
| FROM supabase/realtime:v2.118.0 AS realtime | ||
| FROM supabase/storage-api:v1.67.13 AS storage |
There was a problem hiding this comment.
The GHCR-only Start job pulls storage as ghcr.io/supabase/storage-api:v1.67.13, but the current GHCR storage-api package is not published at that tag. With SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.io, GetRegistryImageUrls returns only that candidate, so the CI start smoke test and GHCR-overridden local starts fail at image pull; mirror v1.67.13 before pinning it here or keep a mirrored storage tag.
Useful? React with 👍 / 👎.
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@d4d559f301e1cc3eb217bfdfd16f96ef21d22c5cPreview package for commit |
Bumps the docker-minor group with 5 updates in the /apps/cli-go/pkg/config/templates directory:
2026.07.13-sha-b5ada962026.07.20-sha-74a0848v2.193.0v2.193.1v2.113.4v2.118.0v1.66.4v1.67.131.47.11.47.2Updates
supabase/studiofrom 2026.07.13-sha-b5ada96 to 2026.07.20-sha-74a0848Updates
supabase/gotruefrom v2.193.0 to v2.193.1Updates
supabase/realtimefrom v2.113.4 to v2.118.0Updates
supabase/storage-apifrom v1.66.4 to v1.67.13Updates
supabase/logflarefrom 1.47.1 to 1.47.2Dependabot 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions