Skip to content

chore(repo): sync develop into next - #7258

Merged
supabase-cli-releaser[bot] merged 2 commits into
nextfrom
sync/develop-into-next
Oct 20, 2026
Merged

supabase-cli-releaser[bot] merged 2 commits into
nextfrom
sync/develop-into-next

Conversation

@supabase-cli-releaser

Copy link
Copy Markdown
Contributor

Merging develop into next conflicts. This branch starts at the tip of develop (f21563c); next is at 8149a66.

Conflicting files:

  • apps/cli-go/pkg/config/templates/Dockerfile

To 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-next

Approve to fast-forward next; do not use the merge button.

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>
@supabase-cli-releaser supabase-cli-releaser Bot added the do not merge Approve to apply; do not merge. label Oct 20, 2026
@supabase-cli-releaser
supabase-cli-releaser Bot requested review from a team and supabase-oss as code owners October 20, 2026 09:02
# Conflicts:
#	apps/cli-go/pkg/config/templates/Dockerfile
@supabase-cli-releaser

Copy link
Copy Markdown
Contributor Author

Claude resolved the merge of next

next removed the whole apps/cli-go tree. On develop, this Dockerfile only had catalog tag bumps (edge-runtime v1.77.6, postgrest v16.5, realtime v2.145.5). Those tags already appear, byte-for-byte the same, in the surviving apps/cli/src/shared/services/Dockerfile and in packages/stack/src/Artifacts.ts, so I deleted the Go copy.

Deleted: apps/cli-go/pkg/config/templates/Dockerfile.

Quick checks. The merged tree passes check:all and unit tests.

Approve to fast-forward next once checks pass (workflow run).

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 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 supabase-oss left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

@supabase-cli-releaser
supabase-cli-releaser Bot merged commit 9914fc1 into next Oct 20, 2026
49 of 50 checks passed
@supabase-cli-releaser
supabase-cli-releaser Bot deleted the sync/develop-into-next branch October 20, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Approve to apply; do not merge.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant