chore(main): release gitops-reverser 0.31.0#206
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Closing as spurious. This PR was generated by release-please during the ~20-minute window while the v0.30.0 GitHub release was still a draft ( main is already at the v0.30.0 release commit (46e0494) with 0 commits since — there is nothing new to release. After re-running the Release Please job now that v0.30.0 is published, release-please correctly reports: Follow-up (separate change): drop |
release-please builds the next release PR in the same invocation that cuts the draft release for the just-merged one, before publish-release flips that draft to published. A draft release is invisible to release-please's "latest release" lookup, so the next PR is computed against the full history and proposes a bogus "release everything" version (it cannot see the release just cut) — e.g. #206 proposed 0.31.0 with a 168-line changelog re-listing work shipped releases ago. Add a close-stale-release-pr job after publish-release: once the release is published, if main has no commits past its tag, close the open 'autorelease: pending' / 'release-please--' PR. release-please opens a fresh, correct one on the next push with releasable commits. Deterministic cleanup; leaves the draft/asset-attachment flow (required for immutable releases) untouched. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
🤖 I have created a release beep boop
0.31.0 (2026-07-07)
⚠ BREAKING CHANGES
Features
Bug Fixes
Performance Improvements
Documentation
This PR was generated with Release Please. See documentation.