Skip to content

fix(release): explain blocked auto-release preflight - #375

Merged
unbraind merged 1 commit into
mainfrom
fix/auto-release-blocked-diagnostics
Jun 26, 2026
Merged

unbraind merged 1 commit into
mainfrom
fix/auto-release-blocked-diagnostics

Conversation

@unbraind

Copy link
Copy Markdown
Owner

Summary

  • add detected preflight state to scheduled Auto Release blocked issues: push, dry_run, release_pat_configured, sentry_personal_admin_token_configured
  • derive a specific detected_cause for missing RELEASE_PAT or missing SENTRY_PERSONAL_ADMIN_TOKEN before falling back to log inspection
  • document that manual push=false/dry_run=true Auto Release runs prove gate health only, not the protected-main publish path
  • record pm evidence on pm-9gxi and pm-7zs0, plus GitHub issue Auto Release blocked: scheduled run failed #374 diagnosis

Verification

  • pnpm build
  • node scripts/run-tests.mjs test -- tests/integration/ci-workflow-contract.spec.ts
  • pnpm quality:static
  • pnpm changelog:pm:check
  • node scripts/run-tests.mjs coverage -> 100/100/100/100 (31815 statements, 24773 branches, 5403 functions, 30538 lines; 256 files, 5132 tests)
  • pnpm audit --audit-level low
  • pnpm security:scan
  • node scripts/release/sentry-telemetry-gate.mjs --json --telemetry-mode best-effort -> Sentry critical=0 high=0, telemetry finish_error_rate_pct=0.73, missing_error_code_rows=0
  • pm health --check-only --summary --json
  • pm validate --check-resolution --check-history-drift --json -> history drift ok; pre-existing resolution warnings tracked by pm-e9zh
  • isolated temp-project smoke in /tmp/pm-cli-release-diagnostics-smoke-oT3SZ2 with sandboxed PM_PATH/PM_GLOBAL_PATH through init/create/claim/update/files/docs/test/comments/test-run/health/validate/close/release

Notes

  • This branch does not and cannot configure the missing RELEASE_PAT secret. Current release env still lists NPM_TOKEN, SENTRY_AUTH_TOKEN, and SENTRY_PERSONAL_ADMIN_TOKEN only; Auto Release blocked: scheduled run failed #374 remains externally blocked until a maintainer adds RELEASE_PAT and reruns Auto Release with push=true.

Add detected preflight state and cause details to scheduled Auto Release failure issues so missing RELEASE_PAT and missing Sentry admin token failures are distinguishable without reading full workflow logs.

Document that manual push=false/dry_run=true Auto Release runs prove gate health only, not the protected-main publish path. Update the CI workflow contract and pm evidence for pm-9gxi and pm-7zs0.

Verification: pnpm build; node scripts/run-tests.mjs test -- tests/integration/ci-workflow-contract.spec.ts; pnpm quality:static; pnpm changelog:pm:check; node scripts/run-tests.mjs coverage (100/100/100/100); pnpm audit --audit-level low; pnpm security:scan; node scripts/release/sentry-telemetry-gate.mjs --json --telemetry-mode best-effort; isolated temp-project smoke with sandboxed PM_PATH/PM_GLOBAL_PATH.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @unbraind, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@coderabbitai

coderabbitai Bot commented Jun 26, 2026 •

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@unbraind, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 35 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI (base), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2054b53b-1f91-45a6-be34-e8e12f5e6534

📥 Commits

Reviewing files that changed from the base of the PR and between 47adaf7 and 3fbd4ea.

📒 Files selected for processing (7)
  • .agents/pm/history/pm-7zs0.jsonl
  • .agents/pm/history/pm-9gxi.jsonl
  • .agents/pm/issues/pm-9gxi.toon
  • .agents/pm/reminders/pm-7zs0.toon
  • .github/workflows/auto-release.yml
  • docs/RELEASING.md
  • tests/integration/ci-workflow-contract.spec.ts
📝 Walkthrough

Walkthrough

The PR updates blocked scheduled auto-release handling to report preflight state and a detected cause, refreshes release-process documentation and contract expectations, and appends matching investigation history, issue, and reminder records.

Changes

Blocked auto-release diagnostics

Layer / File(s) Summary
Workflow alert payload and cause detection
.github/workflows/auto-release.yml
The alert step now passes preflight flags into the shell script, computes detected_cause, and includes the cause plus preflight-state fields in the posted issue body.
Release guidance and contract
docs/RELEASING.md, tests/integration/ci-workflow-contract.spec.ts
docs/RELEASING.md adds notes about the new alert fields and dry-run limits, and the workflow contract test now expects the expanded blocked-run message.
PM tracking records
.agents/pm/history/*.jsonl, .agents/pm/issues/pm-9gxi.toon, .agents/pm/reminders/pm-7zs0.toon
The PM tracking files append investigation evidence, update test and run metadata, and remove assignees while recording the blocked scheduled release follow-up.

Sequence Diagram(s)

sequenceDiagram
  participant Runner as GitHub Actions runner
  participant Workflow as auto-release.yml
  participant Script as scheduled failure script
  participant Issues as GitHub Issues
  Runner->>Workflow: starts scheduled auto-release
  Workflow->>Script: passes INPUT_PUSH, INPUT_DRY_RUN, RELEASE_PAT_CONFIGURED, SENTRY_PERSONAL_ADMIN_TOKEN_CONFIGURED
  Script->>Script: computes detected_cause
  Script->>Issues: posts alert issue body with preflight state
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • unbraind/pm-cli#364: Adds issues: write permissions for the blocked scheduled auto-release alert path updated here.
  • unbraind/pm-cli#366: Updates the same blocked-run preflight messaging around RELEASE_PAT and the matching contract expectations.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: improving blocked auto-release preflight diagnostics.
Description check ✅ Passed The description matches the changeset and summarizes the diagnostics updates and verification.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@unbraind

Copy link
Copy Markdown
Owner Author

@codex review

@unbraind

Copy link
Copy Markdown
Owner Author

@gemini-code-assist review

@unbraind

Copy link
Copy Markdown
Owner Author

/gemini review

@unbraind

Copy link
Copy Markdown
Owner Author

@coderabbitai full review

@chatgpt-codex-connector

Copy link
Copy Markdown

To use Codex here, create a Codex account and connect to github.

@coderabbitai

coderabbitai Bot commented Jun 26, 2026 •

Copy link
Copy Markdown
✅ Action performed

Full review finished.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces diagnostic improvements for blocked scheduled Auto Release runs. It updates the scheduled failure issue template to include preflight state variables (such as release_pat_configured and sentry_personal_admin_token_configured) and a detected cause, allowing agents to easily identify missing release secrets. Additionally, it updates docs/RELEASING.md to clarify that manual dry-runs only verify gate confidence, and updates the integration tests in tests/integration/ci-workflow-contract.spec.ts to assert these new workflow contract requirements. There are no review comments to address, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request enhances the auto-release pipeline's scheduled failure diagnostics by including preflight state information (such as whether RELEASE_PAT and SENTRY_PERSONAL_ADMIN_TOKEN are configured) and the detected cause of failure in the generated issues. It updates docs/RELEASING.md to document these diagnostics and clarify that manual dry-runs only verify gates, not the actual publish path. Additionally, the integration tests in ci-workflow-contract.spec.ts are updated to assert these new workflow contract details, and project management metadata files are updated to track these changes. There are no review comments to address, and I have no additional feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request implements diagnostics for blocked scheduled Auto Release issues. It updates the release documentation and integration tests to ensure that scheduled failure issues include preflight state variables (such as release_pat_configured and sentry_personal_admin_token_configured) and a detected cause, allowing agents to easily identify missing release secrets. Additionally, PM history, issues, and reminders files are updated to track these changes. There are no review comments, so I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant