Repository navigation
chore(repo): sync develop into next - #7192
Conversation
This PR was automatically created to sync API types from the infrastructure repository. Changes were detected after refreshing `apps/cli-go/api/v1-openapi.yaml` from the latest spec from infrastructure, and `apps/cli-go/pkg/api` is regenerated from it. The snapshot diff is the upstream API change and is worth reading: it is marked `linguist-generated`, so GitHub collapses it behind a "Load diff" click rather than hiding it. Co-authored-by: supabase-cli-releaser[bot] <246109035+supabase-cli-releaser[bot]@users.noreply.github.com>
# Conflicts: # apps/cli-go/api/v1-openapi.yaml # apps/cli-go/pkg/api/client.gen.go # apps/cli-go/pkg/api/types.gen.go
Claude resolved the merge of
|
There was a problem hiding this comment.
🤖 AI Review
Both independent reviews reported zero findings. The supplied PR diff is empty, leaving no changed code or findings to adjudicate. This does not establish that the PR is defect-free.
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/38860131074).
Merging
developintonextconflicts. This branch starts at the tip ofdevelop(8c91ac5);nextis at7eb99c3.Conflicting files:
apps/cli-go/api/v1-openapi.yamlapps/cli-go/pkg/api/client.gen.goapps/cli-go/pkg/api/types.gen.goTo 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.