Stop the release reporting failure when the changeset PR is already green

[brentrager]

Problem

The last step of every release run is:

gh pr merge "$PR_NUMBER" --auto --squash

GitHub refuses to enable auto-merge on a PR that is already mergeable:

GraphQL: Pull request is in clean status (enablePullRequestAutoMerge)

So the release run reports failure after it has already versioned, published, and tagged successfully. That is the worst kind of red — everything shipped, the status says it didn't, and people learn to ignore the badge.

Seen live on run 32404388603: Guard, Typecheck, Lint, Test, Build, Format, Version Update 🦋 all ✅ — then Auto-Merge Changeset PR ❌ and the run is failed.

Why now

This was unreachable by accident of timing. PR checks took ~20 minutes, so the changeset PR was always still pending when this step ran and --auto had something to queue behind. Retiring the log-viewer crate (#180) cut PR checks to ~2 minutes, so the changeset PR is now routinely green first and the race inverted.

Fix

Fall back to a plain --squash when --auto is refused — but only after confirming the PR is actually green.

BUCKETS=$(gh pr checks "$PR_NUMBER" --json bucket --jq '[.[].bucket] | join(" ")' || echo "")
if [[ -z "$BUCKETS" ]] || [[ -n "$(tr ' ' '\n' <<<"$BUCKETS" | grep -vx -e pass -e skipping)" ]]; then
  echo "::error::Changeset PR #$PR_NUMBER is not green ([$BUCKETS]); refusing to merge."
  exit 1
fi
gh pr merge "$PR_NUMBER" --squash

It deliberately does not use gh pr checks --required. This repo has no required checks configured, so --required returns an empty list, the grep finds nothing, and it reads as green — a guard that checks the wrong thing and fails open on a merge. An empty bucket list is therefore treated as not green.

Truth table, run locally against the exact expression:

buckets	result
pass	MERGE
pass pass	MERGE
skipping pass	MERGE
(empty)	REFUSE
pass fail	REFUSE
pass pending	REFUSE

🤖 Generated with Claude Code

https://claude.ai/code/session_0152bbE1veqfG1SVJdyLCBxC

[changeset-bot]

⚠️ No Changeset found

Latest commit: a99faf5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR