Skip to content

chore(main): release 0.7.1 - #31

Merged
bougyman merged 1 commit into
mainfrom
release-please--branches--main
Aug 9, 2026
Merged

chore(main): release 0.7.1#31
bougyman merged 1 commit into
mainfrom
release-please--branches--main

Conversation

@ruby-automation

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.7.1 (2026-08-09)

Bug Fixes

  • ci: rebuild the release pipeline to stop the version-bump runaway loop (#30) (c311fd4)

This PR was generated with Release Please. See documentation.

@bougyman
bougyman merged commit 4354326 into main Aug 9, 2026
2 checks passed
@bougyman
bougyman deleted the release-please--branches--main branch August 9, 2026 23:04
bougyman added a commit that referenced this pull request Aug 9, 2026
release-please labels its own release PR "autorelease: pending" and
only relabels it "autorelease: tagged" once it creates the tag itself.
Since we tag it ourselves (gh release create, atomically with the
built assets - required to stay safe under Immutable Releases), that
transition never happened, so release-please's own merged-PR guard
found PR #31 stuck "pending" forever and refused to open PR #32's
release. Relabel it ourselves right after tagging, every time. Also
grants pull-requests: write, needed to edit the label.

Manually fixed PR #31's label already; this makes it automatic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants