Repository navigation
CI gate freshness alert: 1 gate(s) have no recent completed main result #8085
Description
The following post-merge gates have not produced a completed main result within their freshness budget.
This usually means they are starved, not broken — queued behind a merge cadence the runner pool cannot drain (#7856). Check the Actions queue depth before assuming a code failure:
gh api "repos/PerryTS/perry/actions/runs?status=queued&per_page=100" \
-q '.workflow_runs | length'| gate | detail | why it matters |
|---|---|---|
npm-publish-freshness.yml |
NO completed post-merge result in the sampled window | Daily comparison of npm's latest against this tree (#7491: users installed a month-old build and hit a linker bug fixed weeks earlier). A completed failure is fresh execution evidence here; the workflow's own sticky issue carries the overdue-registry verdict. |
Scheduling rationale and the cost it trades away: docs/src/testing/ci-gate-scheduling.md.
This issue is maintained automatically by gate-freshness.yml. It is updated in place, never duplicated, and closes itself once every gate is fresh again.
Activity
[-]CI gate freshness alert: 1 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 4 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 4 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 4 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 4 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 4 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 4 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/+][-]CI gate freshness alert: 3 gate(s) have no recent successful `main` run[/-][+]CI gate freshness alert: 2 gate(s) have no recent successful `main` run[/+]fix(ci): track completed gate results (#8085) (#8312)
github-actions commentedon Aug 17, 2026
All post-merge gates are fresh again; closing automatically.
106 remaining items
github-actions commentedon Oct 5, 2026
All post-merge gates are fresh again; closing automatically.
[-]CI gate freshness alert: 5 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 2 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 2 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 4 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 4 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 1 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 1 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 4 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 4 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 1 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 1 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 11 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 11 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 3 gate(s) have no recent completed `main` result[/+][-]CI gate freshness alert: 3 gate(s) have no recent completed `main` result[/-][+]CI gate freshness alert: 1 gate(s) have no recent completed `main` result[/+]github-actions commentedon Oct 9, 2026
All post-merge gates are fresh again; closing automatically.
github-actions commentedon Oct 12, 2026
All post-merge gates are fresh again; closing automatically.