73d91725a95c284416d4dc3447bda223da393a89
* fix(plugin-release): correct PR merge logic for BLOCKED state Prior releases failed with 'Resource not accessible by integration' when gh pr merge was called with a branch name on a BLOCKED PR. The root cause is that --auto requires the PR to have a pending status check that can be satistfied by auto-merge. Without --auto, gh attempts an immediate merge but the BLOCKED state (from branch protection requiring status checks) causes GitHub to reject the push. Fix: always use --auto for BLOCKED PRs, and refactor the polling loop so it properly loops until mergeStateStatus is no longer UNKNOWN (up to 3 retries with exponential back-off) before deciding whether to use --auto or merge directly. Also fix the case where gh pr create is called without --json output, so OPEN_PR is always captured correctly regardless of whether we created a new PR or found a pre-existing one. Co-Authored-By: Paperclip <noreply@paperclip.ing> * fix: restore MERGED check and use PR number in retry loop - Restore idempotent exit 0 when PR is already MERGED (regression from prior fix) - Use $OPEN_PR instead of hardcoded branch name in gh pr view retry loop - Fallback to --auto when UNKNOWN persists after exhausting retries (safe: auto-merge waits for branch protection) Fixes bugs reported by Regression Regina on PR #133. --------- Co-authored-by: Chris Farhood <chris@farhood.org> Co-authored-by: Paperclip <noreply@paperclip.ing>
Description
Languages
Shell
100%