Skip to content

fix: release-please auto-merge + tag-move work without a checkout#23

Merged
roleme merged 1 commit into
mainfrom
fix/release-please-automerge-parse
Jun 26, 2026
Merged

fix: release-please auto-merge + tag-move work without a checkout#23
roleme merged 1 commit into
mainfrom
fix/release-please-automerge-parse

Conversation

@roleme

@roleme roleme commented Jun 26, 2026

Copy link
Copy Markdown
Owner

Why

Follow-up to #21. The release PR (#22) was created correctly via the PAT and zizmor went green, but it did not auto-merge.

Root cause: the "Enable auto-merge" step called gh pr view <n> to read the title, but this job has no actions/checkout, so gh had no repo to infer and failed with not a git repository → version parse empty → every PR fell through to "leaving for manual review".

The major-tag-move step had the same latent bug (it used local git tag/git push in a checkout-less job) and would have failed the first time a release was actually cut.

Fix

  • Parse number + title straight from steps.release.outputs.prs (already a JSON array — no gh pr view needed) and pass --repo to gh pr merge.
  • Replace the local-git tag-move with a REST API create-or-update of refs/tags/vN using the PAT.

After this merges, release-please re-runs and PR #22 should auto-merge once its zizmor check is green.

🤖 Generated with Claude Code

The auto-merge step ran `gh pr view` but the job has no checkout, so gh had
no repo context and the call failed ("not a git repository"), leaving every
release PR unmerged. Parse the number+title directly from steps.release
.outputs.prs (already JSON) and pass --repo to `gh pr merge`.

The major-tag-move step likewise relied on local git in a checkout-less job;
switch it to the REST API (create-or-update ref) using the PAT.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@roleme roleme merged commit 6bab1e3 into main Jun 26, 2026
1 check passed
@roleme roleme deleted the fix/release-please-automerge-parse branch June 26, 2026 11:43
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