Repository navigation
chore(repo): sync develop into next - #7190
Conversation
This bumps realtime from v2.144.0-r0 to v2.144.2-r0. https://github.com/supabase/slim-services/releases/tag/realtime-v2.144.2-r0 Planned after supabase/slim-services published v2.144.1-r0. This branch is rewritten from develop whenever a newer relevant release arrives. Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
# Conflicts: # apps/cli-go/pkg/config/templates/Dockerfile
Claude resolved the merge of
|
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews completed with no findings. Inspection of the changed files and surrounding code confirms that Realtime v2.144.2 is consistently pinned across the Dockerfile and artifact catalog, following trusted ADR 0026. No actionable issues found. Remote artifact availability and digest contents were not independently verified.
Findings
No issues found.
Stats
Claude findings: 0 · Codex findings: 0 · Confirmed: 0 · Refuted: 0 · Uncertain: 0
Models: claude-opus-5-5 + gpt-6.1-sol · Trigger: manual · Workflow run
This review runs once per PR. A maintainer can request another with a /ai-review comment.
supabase-oss
left a comment
There was a problem hiding this comment.
CI is green and the AI review raised nothing the merge introduced, so this approves Claude's resolution of the sync (https://github.com/supabase/cli/actions/runs/38848054735).
Merging
developintonextconflicts. This branch starts at the tip ofdevelop(88a35b9);nextis atb7add97.Conflicting files:
apps/cli-go/pkg/config/templates/DockerfileTo resolve:
git fetch origin git switch sync/develop-into-next git merge origin/next # resolve the conflicts, then commit git push origin sync/develop-into-nextApprove to fast-forward
next; do not use the merge button.