Skip to content

Auto Release blocked: scheduled run failed #492

Closed

Description

@github-actions

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

Run: https://github.com/unbraind/pm-cli/actions/runs/29073827938
Commit: 1bdca53
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 10, 2026

    @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 10, 2026

    @unbraind
    Owner

    Resolved by #493 (merged as 798aed4). Live production-token validation now reports zero blocking high/critical Sentry issues while retaining an explicit regression that an isUnhandled=true twin still blocks. Closing this same-day bot-created blocker intentionally exercises the Auto Release issue-retry path.

  3. unbraind commented on Jul 10, 2026

    @unbraind
    Owner

    CodeRabbit issue-enrichment comment 4932667520 was read and upvoted. Its related-PR lineage was useful; no generated implementation plan is needed because #493 is merged, PM-CLI-1X is resolved, and the same-day recovery run is now active.

  4. github-actions commented on Jul 10, 2026

    @github-actions
    Author

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

  5. github-actions commented on Jul 10, 2026

    @github-actions
    Author

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

    Run: https://github.com/unbraind/pm-cli/actions/runs/29082546688
    Commit: abb1a52

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

  6. unbraind commented on Jul 10, 2026

    @unbraind
    Owner

    Automation feedback acknowledgment: github-actions comments 4933863882 and 4933987747 were both read and upvoted. The retry marker correctly prevented duplicate same-day attempts, and the success comment confirms v2026.7.10, release commit abb1a52, and downstream Release completion.

  7. unbraind commented on Jul 11, 2026

    @unbraind
    Owner

    pm tracker item:

    • pm-9gxi — Auto Release blocked: bot cannot push version commit to protected main (GH006, 12 required checks)
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