You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
detected_cause: Inspect the failed workflow logs for the exact failing command.
Common causes:
RELEASE_PAT is missing from the release environment, so Auto Release cannot push its checked version commit/tag to protected main.
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.
#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 plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.
Create Plan
🧪 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:
issue_enrichment:
auto_enrich:
enabled: false
💬 Have feedback or questions? Drop into our discord!
Canonical PM item: pm-u1baah. This link preserves the implementation lineage, dependencies, decisions, and verification evidence in the project system of record.
Activity
coderabbitai commentedon Aug 7, 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 7, 2026
Canonical PM item: pm-u1baah. This link preserves the implementation lineage, dependencies, decisions, and verification evidence in the project system of record.
github-actions commentedon Aug 8, 2026
Superseded by a new Auto Release blocker for the current UTC day.
Run: https://github.com/unbraind/pm-cli/actions/runs/31238168668
Commit: 3e26856
Closing this stale blocker so same-day retry detection uses the most recent scheduled failure date.