Repository navigation
Auto Release blocked: scheduled run failed #1045
Description
The scheduled daily Auto Release run did not complete. A tag or npm package may already exist if the downstream Release workflow failed after publication; inspect the live tag, npm, and GitHub Release states before retrying.
Run: https://github.com/unbraind/pm-cli/actions/runs/31991277386
Commit: 7668c2e
Trigger: schedule
Detected preflight state:
- push:
true - dry_run:
false - release_pat_configured:
true - sentry_personal_admin_token_configured:
true - failing_stage:
unrecorded - detected_cause: No gate recorded a verdict and the release environment is fully configured; 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). - Post-publish package execution or GitHub Release verification failed after npm accepted the package.
Inspect the live release state and failed logs first; then configure the release token, resolve the gate's blocking_short_ids, or fix post-publish verification as indicated. This issue is auto-updated so blocked daily releases are never silently skipped.
Reacted by coderabbitai
Activity
coderabbitai commentedon Aug 17, 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 Aug 17, 2026
Canonical PM lineage: pm-dm2vfz (active fix), implementing pm-uenmu9 and discovered from the delayed-schedule evidence in pm-44u3wt.
The production release itself succeeded: Auto Release 31990359112 published immutable v2026.8.17 at 7668c2e, downstream Release 31990927326 passed, npm latest is 2026.8.17, and independent npx/bunx acceptance passes. The queued scheduled run 31991277386 then failed before build because it evaluated reviewed-PR analyzer provenance on that generated release commit before recognizing the already-published same-day result. No duplicate release occurred. This issue remains open only until the queued automatic no-op path is fixed and verified.
unbraind commentedon Aug 17, 2026
Acknowledged the CodeRabbit enrichment. The related historical PRs are useful context; the actionable scope is narrower and is recorded in pm-dm2vfz: recognize a fully published current-day release before analyzer provenance, while refusing tag-only or incomplete publication. The fix will include a schedule/manual concurrency negative control and preserve one automatic release per UTC day.
github-actions commentedon Aug 17, 2026
Auto Release retry attempt recorded for 2026-08-17 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 Aug 17, 2026
Auto Release retry after blocker resolution succeeded and published
v2026.8.17.Run: https://github.com/unbraind/pm-cli/actions/runs/31995854207
Commit: 7668c2e
The blocker remains closed because the retry pushed a release tag and the downstream Release workflow completed successfully.