supabase / cli / 37643943509
67%
develop: 67%

LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7185-1c2ac9f974810757e4d8ba876ddd0861dd9114a8
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 79
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.737%. Remained the same
37643943509

push

github

web-flow 
ci(release): add next channel, maintenance lines and guarded promotions (CLI-2630) (#7038)

## Summary

Sets up the branching and release machinery from
[CLI-2630](https://linear.app/supabase/issue/CLI-2630/gh-branch-and-release-process)
so we can start merging breaking-change work for v3. The design (and the
review rounds behind it) lives in the Linear issue; the canonical
runbook is now in `apps/cli/docs/release-process.md`, with ADR 0028
superseding ADR 0011's dist-tag section.

### What changes

**New `next` channel**
- `next` is a long-lived branch for breaking work. Breaking PRs target
it with a `type(scope)!:` title.
- semantic-release treats it as a `next` prerelease branch, so it
publishes `X.Y.Z-next.N`. It goes out to npm `next` and as a GitHub
prerelease, with no brew/scoop.
- In `release.yml`, a push to `next` runs `test.yml` first, and only
plans and releases once that passes.
- `-next.N` builds identify as "Supabase CLI (next channel)."

**Syncing (`sync-branches.yml`, replaces `sync-main-to-develop.yml`)**
- Two pairs only: main → develop after a stable release, and develop →
next on every develop push.
- A clean merge is pushed directly.
- On a conflict it opens a `sync/<source>-into-<target>` PR at the
source tip and pauses that pair until the PR closes. Someone resolves it
by merging the target in.

**Approve-to-fast-forward (`fast-forward.yml`, moved out of
`release.yml`)**
- Covers the deploy PR (develop → main), the major cut (next → develop),
and the two bot-authored sync PRs.
- Before pushing it checks:
  - the approver has write access
  - the approved commit is still the PR head
- the 4 required checks are green, read from this PR's own check rollup
so another PR's runs on the same commit don't count
- `--ff-only` (sync PRs re-sync and ask for re-approval if the target
moved)
- Anything that lands on `main` also refuses a major bump without the
`release-major` label.
- `test.yml` now runs on PRs into `main`, so the deploy PR ... (continued)

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37643943509.1 79
66.74
GitHub Action Run
Source Files on build 37643943509