Repository navigation
chore(repo): sync develop into next - #7227
Conversation
This bumps studio from 2026.10.12-sha-3699278-r0 to 2026.10.19-sha-b375769-r0. https://github.com/supabase/slim-services/releases/tag/studio-2026.10.19-sha-b375769-r0 Planned after supabase/slim-services published 2026.10.19-sha-b375769-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 reported no findings. Code inspection confirms the sync resolution deletes the obsolete Go Dockerfile while preserving the Studio update in the surviving TypeScript Dockerfile and artifact catalog. No issues introduced by the sync resolution were identified.
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/39202853151).
Merging
developintonextconflicts. This branch starts at the tip ofdevelop(ff0cd0c);nextis atb8d414e.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.