Repository navigation
chore(repo): sync develop into next - #7258
Conversation
This bumps edge-runtime from v1.77.5-r0 to v1.77.6-r0. https://github.com/supabase/slim-services/releases/tag/edge-runtime-v1.77.6-r0 Planned after supabase/slim-services published v1.77.6-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. Verified that the sync resolution preserves deletion of the obsolete Go Dockerfile, with no remaining code references to it. The active TypeScript Dockerfile and artifact catalog consistently pin edge-runtime v1.77.6. No issues found within the sync-review scope.
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/39398472475).
Merging
developintonextconflicts. This branch starts at the tip ofdevelop(f21563c);nextis at8149a66.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.