Skip to content

Auto Release blocked: scheduled run failed #432

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

Description

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

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

Run: https://github.com/unbraind/pm-cli/actions/runs/28731921751
Commit: 010bb34

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 5, 2026

    @coderabbitai
    coderabbitaiBot
    on Jul 5, 2026 – with coderabbitai
    🔗 Related PRs

    #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]
    #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]

    📝 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 5, 2026

    @unbraind
    unbraind
    on Jul 5, 2026
    Owner

    Investigated on current main after PR #434 merged. The scheduled run failed in scripts/release/run-gates.mjs because it invoked scripts/release/static-quality-gate.mjs directly, which uses the 100% default docstring thresholds. The project lint path intentionally uses the ratcheted pnpm quality:static thresholds while the repo-wide 100% docstring fill work remains tracked under pm-4ak1/pm-5566.

    Fix branch: codex/auto-release-static-ratchet

    Patch: run-gates now calls pnpm quality:static for the static-quality step, with unit and release-automation contract coverage to prevent drift back to the raw defaults.

    Verification passed locally:

    • node scripts/run-tests.mjs test -- tests/unit/scripts/release/run-gates.spec.ts tests/integration/release-automation-contract.spec.ts
    • node scripts/release/run-gates.mjs --telemetry-mode off --skip-greptile (static quality passed, full coverage 100/100/100/100 over 264 files and 5423 tests, npx smoke, package-first dogfood, compatibility, telemetry-off gate)
    • pnpm lint
    • pnpm changelog:pm:check unchanged with pm-changelog 2026.6.30
    • pm health --check-only --summary --json ok
    • pm validate --check-resolution --check-history-drift --json ok for history drift; existing resolution metadata backlog remains 268 items

  3. unbraind commented on Jul 5, 2026

    @unbraind
    unbraind
    on Jul 5, 2026
    Owner

    Fixed by merged PR #447 (c8abb9957c70ce1f43c8dbd76d8b94c0492407f7). The auto-release gate now invokes the ratcheted pnpm quality:static package script instead of the raw static-quality script defaults. Local verification on the merged head passed node scripts/release/run-gates.mjs --telemetry-mode off --skip-greptile, pnpm lint, pnpm changelog:pm:check, pm health --check-only --summary --json, and pm validate --check-resolution --check-history-drift --json with only the known pre-existing validate_resolution_missing_fields:268 warning.

  4. unbraind commented on Jul 5, 2026

    @unbraind
    unbraind
    on Jul 5, 2026
    Owner

    Closing after PR #447 merged to main and post-merge verification completed on c8abb9957c70ce1f43c8dbd76d8b94c0492407f7. The latest scheduled failure listed in Actions is still the pre-fix 2026-07-05 run on old SHA 010bb349; the next scheduled Auto Release will verify the production cron path with the ratcheted gate.

  5. unbraind
    closed this as completedon Jul 5, 2026

  6. unbraind commented on Jul 5, 2026

    @unbraind
    unbraind
    on Jul 5, 2026
    Owner

    Bot acknowledgement: reacted to CodeRabbit issue enrichment #432 (comment). I reused the existing release-health pm lineage (pm-7zs0) and fixed the code-side release-gate root cause in PR #447 rather than creating a duplicate tracker item.

  7. unbraind commented on Jul 11, 2026

    @unbraind
    unbraind
    on Jul 11, 2026
    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