Found while cutting v2.0.0 (run 31908267995). Two independent bugs mean the Release workflow cannot currently ship a release:
-
Argument mangling breaks explicit release types. The workflow runs pnpm release -- --release-as <type>. pnpm inserts an extra --, so commit-and-tag-version receives the flags as positional junk and falls back to auto-detection — dispatching with major produced a 1.2.0 minor bump instead of 2.0.0, and pushed a stray v1.2.0 tag (since deleted). Fix: call pnpm exec commit-and-tag-version --release-as <type> directly.
-
The version-bump push to main is rejected by the branch ruleset. main branch protection requires PRs + 4 status checks, and the only bypass actor is a user account — GITHUB_TOKEN (github-actions bot) has no bypass, so git push --follow-tags origin main fails with GH013. Note the tag ref still goes through before the branch ref is rejected, which is how the stray tag escaped. Fix options: (a) add the workflow/app as a ruleset bypass actor, or (b) rework the workflow to open a release PR and publish the tag+release after merge.
v2.0.0 was shipped manually (local commit-and-tag-version + push with the bypass account, then gh release create). The workflow remains broken for future releases until this is fixed.
🤖 Generated with Claude Code
Found while cutting v2.0.0 (run 31908267995). Two independent bugs mean the Release workflow cannot currently ship a release:
Argument mangling breaks explicit release types. The workflow runs
pnpm release -- --release-as <type>. pnpm inserts an extra--, so commit-and-tag-version receives the flags as positional junk and falls back to auto-detection — dispatching withmajorproduced a 1.2.0 minor bump instead of 2.0.0, and pushed a stray v1.2.0 tag (since deleted). Fix: callpnpm exec commit-and-tag-version --release-as <type>directly.The version-bump push to main is rejected by the branch ruleset.
main branch protectionrequires PRs + 4 status checks, and the only bypass actor is a user account —GITHUB_TOKEN(github-actions bot) has no bypass, sogit push --follow-tags origin mainfails with GH013. Note the tag ref still goes through before the branch ref is rejected, which is how the stray tag escaped. Fix options: (a) add the workflow/app as a ruleset bypass actor, or (b) rework the workflow to open a release PR and publish the tag+release after merge.v2.0.0 was shipped manually (local commit-and-tag-version + push with the bypass account, then
gh release create). The workflow remains broken for future releases until this is fixed.🤖 Generated with Claude Code