Repository navigation
Auto Release blocked: scheduled run failed #521
Description
The scheduled daily Auto Release run failed before publishing, so no release was cut.
Run: https://github.com/unbraind/pm-cli/actions/runs/29181568390
Commit: c7b56e7
Trigger: schedule
Detected preflight state:
- push:
true - dry_run:
false - release_pat_configured:
true - sentry_personal_admin_token_configured:
true - detected_cause: Inspect the failed workflow logs for the exact failing command.
Common causes:
RELEASE_PATis missing from the release environment, so Auto Release cannot push its checked version commit/tag to protectedmain.- The Sentry/telemetry reliability gate blocked on an unresolved fatal/error issue inside its recent-activity window (
--sentry-window-days).
Configure the release push token or resolve the gate's blocking_short_ids, then re-run Auto Release. This issue is auto-updated so blocked daily releases are never silently skipped.
Reacted by coderabbitai
Activity
coderabbitai commentedon Jul 12, 2026
🔗 Related PRs
#366 - Fix protected-main auto-release token and contracts namespaces [merged]
#375 - fix(release): explain blocked auto-release preflight [merged]
#392 - [codex] Resolve stale auto-release blockers after scheduled publish [merged]
#406 - feat(mcp): extension-aware built-in actions + action-scoped name schema (pm-zumn, pm-fq80) [merged]
#451 - Retry auto release after blocker resolution [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
unbraind commentedon Jul 12, 2026
pm tracker item: pm-wfvq
Root cause: the sentry-telemetry-gate blocked on PM-CLI-26 / PM-CLI-10 — both torn-install bundle transients on a dogfood host (hashed chunk from a stale build generation;
chunk-IV4NIS5E.jsexists in no current build). Not shipped regressions in 2026.7.11. Both Sentry issues verified non-reproducible against a healthy install and resolved; Auto Release re-run follows. pm-wfvq owns the class fix (boot-time bundle-integrity self-check + distinct error code the gate can classify safely).chore(pm): recover blocked 2026.7.12 release, reconcile PR#520 lane, …
unbraind commentedon Jul 12, 2026
Recovered: v2026.7.12 published (npm + GitHub release, publish run 29182944895 success). The blocking Sentry issues PM-CLI-26/PM-CLI-10 were torn-install transients, resolved after live verification; class fix tracked in pm-wfvq. Note for future manual recoveries:
gh workflow run "Auto Release"defaultspush=false(cuts the version but publishes nothing) — pass-f push=true.chore(pm): confirm 2026.7.12 recovery on pm-7zs0 (publish verified, G…
github-actions commentedon Jul 12, 2026
Auto Release retry attempt recorded for 2026-07-12 UTC.
This marker prevents repeated production retries for the same blocker issue if the retry fails and the issue is closed again before UTC midnight.
github-actions commentedon Jul 12, 2026
Auto Release retry after blocker resolution completed without publishing a new tag.
Run: https://github.com/unbraind/pm-cli/actions/runs/29183414443
Commit: 8091489
Retry skip reason:
no_new_pushed_release_tagThe retry completed but found no new pushed release tag, usually because no publish-eligible changes remained after the latest release tag.
The blocker remains closed because the retry path did not fail.