Skip to content

Auto Release blocked: scheduled run failed #653

New issue
New issue
Closed
Closed
Auto Release blocked: scheduled run failed#653

Description

@github-actions
github-actions
bot
opened on Jul 23, 2026

The scheduled daily Auto Release run failed before publishing, so no release was cut.

Run: https://github.com/unbraind/pm-cli/actions/runs/29982743761
Commit: 47f7f1f
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_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).

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.

Activity

  1. coderabbitai commented on Jul 23, 2026

    @coderabbitai
    coderabbitaiBot
    on Jul 23, 2026 – with coderabbitai
    🔗 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 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!

  2. unbraind commented on Jul 23, 2026

    @unbraind
    unbraind
    on Jul 23, 2026
    Owner

    Canonical pm tracking after an all-status duplicate check:

    • pm-k9t17l owns the exact self-edge defect and Sentry PM-CLI-2J resolution.
    • pm-7zs0 owns daily published-release verification.

    PR #652 fixes the blocking exception and is fully green; no duplicate release-blocker pm item was created.

  3. unbraind commented on Jul 23, 2026

    @unbraind
    unbraind
    on Jul 23, 2026
    Owner

    CodeRabbit enrichment 5054916751 acknowledged. The related historical release PRs are useful lineage; the current failure is already narrowed to Sentry PM-CLI-2J and tracked by pm-k9t17l, so no separate implementation plan is needed.

  4. unbraind commented on Jul 23, 2026

    @unbraind
    unbraind
    on Jul 23, 2026
    Owner

    Recovery preconditions are now satisfied on merged main 0c2928f:

    • PR SDK context integrity and merge truth #652 merged with 29 successful / 0 failing checks.
    • merged installed CLI rejects the self edge with usage exit 2 and writes no item/history state.
    • Sentry PM-CLI-2J is resolved in the next release with no events after 2026-07-22T21:40:25Z.
    • strict live reliability gate passes: critical=0, high=0, telemetry finish error rate=0.68%, missing error-code rows=0.

    Closing this same-day blocker intentionally triggers the guarded Auto Release retry.

  5. unbraind
    closed this as completedon Jul 23, 2026

  6. github-actions commented on Jul 23, 2026

    @github-actions
    github-actionsBot
    on Jul 23, 2026 – with GitHub Actions
    Author

    Auto Release retry attempt recorded for 2026-07-23 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.

  7. github-actions commented on Jul 23, 2026

    @github-actions
    github-actionsBot
    on Jul 23, 2026 – with GitHub Actions
    Author

    Auto Release retry after blocker resolution succeeded and published v2026.7.23.

    Run: https://github.com/unbraind/pm-cli/actions/runs/29983501824
    Commit: 1206c26

    The blocker remains closed because the retry pushed a release tag and the downstream Release workflow completed successfully.

  8. unbraind commented on Jul 23, 2026

    @unbraind
    unbraind
    on Jul 23, 2026
    Owner

    GitHub Actions retry marker 5054974935 acknowledged: the guarded same-day attempt was recorded exactly once before production mutation.

  9. unbraind commented on Jul 23, 2026

    @unbraind
    unbraind
    on Jul 23, 2026
    Owner

    GitHub Actions success report 5055066730 acknowledged: v2026.7.23 published from release commit 1206c26 and downstream Release run 29983848608 completed successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions