chore(cli): downgrade realtime image to v2.108.0 - #5628
Conversation
Realtime v2.109.0 (supabase/realtime#1954, "least-privilege realtime user") adds a new migration, 20260606120000_setup_supabase_realtime_admin, that does not exist in v2.108.0. When the CLI runs realtime once to apply migrations during local schema init (initSchema15 -> `realtime eval ... ensure_all_started(:realtime)`), that migration's ALTER ROLE / GRANT statements fail against the local supabase/postgres image, so the container exits 1 and `supabase start` fails. The docker-minor bump (#5625) to v2.109.1 turned the Start CI job red on every run since. Pin realtime back to the last known-good v2.108.0 until the new migration is compatible with the CLI's local stack. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RLY7KJJ6So673p6ung8yFV
![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: d35e3b837e
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| FROM supabase/supavisor:2.9.7 AS supavisor | ||
| FROM supabase/gotrue:v2.190.0 AS gotrue | ||
| FROM supabase/realtime:v2.109.1 AS realtime | ||
| FROM supabase/realtime:v2.108.0 AS realtime |
There was a problem hiding this comment.
This pin is in the Dockerfile that .github/dependabot.yml scans for Docker updates, and that config still groups minor/patch Docker updates for this directory while excluding supabase/* images from cooldown. Because supabase/realtime:v2.109.1 was already available and was the version being reverted here, the next scheduled Dependabot run can immediately propose the same broken bump again unless supabase/realtime is ignored or otherwise held back.
Useful? React with 👍 / 👎.
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@2b1340aa4c4365fb92eb9fa5422e5ff4939e7b16Preview package for commit |
The realtime pin let `supabase start` progress past schema init, exposing a second regression from the same docker-minor bump (#5625): the CI registry (ghcr) has no mirror for supabase/logflare:1.45.0, so pulling it fails with "manifest unknown". Pin logflare back to the last mirrored tag 1.44.3. Also add Dependabot ignore rules so the docker-minor group does not immediately re-propose the same broken versions: - supabase/realtime >= 2.109.0 (incompatible migration vs local Postgres) - supabase/logflare >= 1.45.0 (not mirrored to ghcr) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RLY7KJJ6So673p6ung8yFV
## What kind of change does this PR introduce? - Revert supabase#5628 fixed by supabase/realtime#1984 - Sync template/tests to latest Realtime version ## What is the current behavior? Realtime update blocked. Co-authored-by: Andrew Valleteau <avallete@users.noreply.github.com>
3 participants
Downgrades the Supabase Realtime Docker image from v2.109.1 to v2.108.0 in the generated Dockerfile template.
This change updates the base image version used in the CLI's Docker configuration for local development environments.
https://claude.ai/code/session_01RLY7KJJ6So673p6ung8yFV