supabase / cli / 37047553264
67%
develop: 67%

LAST BUILD BRANCH: juliengoux/cli-2688-stack-mode-lockable-service-versions-with-hosted-parity-via
DEFAULT BRANCH: develop
Ran
Jobs 1
Files 79
Run time 1min
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
37047553264

push

github

web-flow 
ci(stack): retry slim pickup when a merge-queued PR holds the branch (#6957)

`slim-release-published.yml` force-pushes one branch per service release
line. When that branch's PR sits in the merge queue, GitHub rejects the
push (GH006) and the job used to fail, dropping the planned pin until
the next upstream release. On 2026-10-01 this lost edge-runtime
v1.77.4-r0: the v1.77.3-r0 and v1.77.4-r0 dispatches both hit
`slim-bump/edge-runtime` while #6930 was queued (restored by #6955).

When a push is rejected because the branch is queued for merging, the
Apply step now:

- waits for the queue to merge or drop that PR, polling `isInMergeQueue`
for up to 30 minutes and within the app token's lifetime;
- stops processing the current plan, so no remaining item is built from
the pre-merge base;
- re-sends the same dispatch so a fresh run re-plans from the updated
default branch, at most three times in a row (tracked by a validated
`client_payload.replay` counter).

The concurrency group now keeps every pending run (`queue: max`) instead
of replacing the pending one, so a replay can never cancel a newer
dispatch and its release-visibility wait. A failed queue lookup or
dispatch, a queue that holds the branch past the deadline, an exhausted
replay budget, and any other push rejection still fail the run with the
manual recovery command. ADR 0026 documents the behavior.

4097 of 6139 relevant lines covered (66.74%)

7.37 hits per line

Jobs
ID Job ID Ran Files Coverage
1 37047553264.1 79
66.74
GitHub Action Run
Source Files on build 37047553264