Auto Release blocked: scheduled run failed #374

Activity

1. coderabbitai commented on Jun 26, 2026

   

   coderabbitaiBot

   on Jun 26, 2026 – with coderabbitai

   More actions

   🔗 Related PRs

   #305 - fix(release): bound Sentry gate to a recent-activity window + alert on blocked daily releases [merged]
   #364 - fix(ci): grant issues:write so the blocked auto-release alert can open its tracking issue [merged]
   #366 - Fix protected-main auto-release token and contracts namespaces [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 Jun 26, 2026

   

   unbraind

   on Jun 26, 2026

   Owner

   More actions

   Current diagnosis from this branch: scheduled Auto Release run 28221678293 failed before running the release pipeline because RELEASE_PAT_CONFIGURED=false. The release environment currently lists NPM_TOKEN, SENTRY_AUTH_TOKEN, and SENTRY_PERSONAL_ADMIN_TOKEN, but no RELEASE_PAT; main branch protection still requires the checked version commit to satisfy 12 checks, so the default GITHUB_TOKEN cannot be used for the production push. Manual run 28219218329 was push=false and dry_run=true, so it proved release gates only, not the protected-main publish path. I am adding workflow diagnostics so future blocked-release issues include the detected preflight state and cause directly in the issue body.
3. github-actions commented on Jun 27, 2026

   

   github-actionsBot

   on Jun 27, 2026 – with GitHub Actions

   Author

   More actions

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

   Run: https://github.com/unbraind/pm-cli/actions/runs/28280770086
   Commit: b7d4dcc

   Detected preflight state:

   • push: true
   • dry_run: false
   • release_pat_configured: false
   • sentry_personal_admin_token_configured: true
   • detected_cause: RELEASE_PAT is missing from the release environment; scheduled production releases cannot push the checked version commit/tag to protected main.

   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.
4. github-actions commented on Jun 28, 2026

   

   github-actionsBot

   on Jun 28, 2026 – with GitHub Actions

   Author

   More actions

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

   Run: https://github.com/unbraind/pm-cli/actions/runs/28314163942
   Commit: ddd7442

   Detected preflight state:

   • push: true
   • dry_run: false
   • release_pat_configured: false
   • sentry_personal_admin_token_configured: true
   • detected_cause: RELEASE_PAT is missing from the release environment; scheduled production releases cannot push the checked version commit/tag to protected main.

   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.
5. github-actions commented on Jun 29, 2026

   

   github-actionsBot

   on Jun 29, 2026 – with GitHub Actions

   Author

   More actions

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

   Run: https://github.com/unbraind/pm-cli/actions/runs/28355069277
   Commit: 5db0422

   Detected preflight state:

   • push: true
   • dry_run: false
   • release_pat_configured: false
   • sentry_personal_admin_token_configured: true
   • detected_cause: RELEASE_PAT is missing from the release environment; scheduled production releases cannot push the checked version commit/tag to protected main.

   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.
6. unbraind

   added a commit that references this issue on Jun 29, 2026

   chore(pm): close extension profile SDK lineage (#402)

   ...

   8351fde
7. github-actions commented on Jun 30, 2026

   

   github-actionsBot

   on Jun 30, 2026 – with GitHub Actions

   Author

   More actions

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

   Run: https://github.com/unbraind/pm-cli/actions/runs/28425418015
   Commit: e2f2dd7

   Detected preflight state:

   • push: true
   • dry_run: false
   • release_pat_configured: false
   • sentry_personal_admin_token_configured: true
   • detected_cause: RELEASE_PAT is missing from the release environment; scheduled production releases cannot push the checked version commit/tag to protected main.

   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.
8. unbraind

   added a commit that references this issue on Jun 30, 2026

   fix(mcp): clear partial extension registries before fallback

   ...

   8cd4816
9. unbraind commented on Jun 30, 2026

   

   unbraind

   on Jun 30, 2026

   Owner

   More actions

   Release blocker resolved on 2026-06-30. RELEASE_PAT is now configured in the release environment (verified with gh secret list; token value not exposed), and Auto Release successfully pushed the protected-main release commit/tag for v2026.6.30. The downstream tag-push Release workflow published npm @unbrained/pm-cli@2026.6.30 and created GitHub Release v2026.6.30. I also cleaned up an accidental manual same-day validation attempt before it published: cancelled Auto Release run 28435255578 and Release run 28435694926, deleted the stray v2026.6.30-2 tag, and pushed revert commit ff76150 so package.json/CHANGELOG.md match npm latest 2026.6.30. Follow-up hardening commit d5cffa5 removes the Auto Release workflow_dispatch same-day override so GitHub Actions follows the one-production-release-per-day policy. I am not triggering another production Auto Release today; the next scheduled run will use the fixed secret path only if there are real non-tracker changes after the latest release.
10. unbraind

    closed this as completedon Jun 30, 2026
11. unbraind commented on Jul 11, 2026

    

    unbraind

    on Jul 11, 2026

    Owner

    More actions

    pm tracker item:

    • pm-9gxi — Auto Release blocked: bot cannot push version commit to protected main (GH006, 12 required checks)