chore(main): release gitops-reverser 0.30.0#196
Closed
github-actions[bot] wants to merge 1 commit into
Closed
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
sunib
added a commit
that referenced
this pull request
Jul 6, 2026
release-please lost its last-release baseline after the failed 0.29.1 release was manually deleted: with the 0.29.1 GitHub release gone (its tag still present, but no release), release-please walked back to ~v0.27.1 and opened a release PR (#196) proposing 0.30.0 that re-lists 168 already-shipped commits and re-declares breaking changes released back in v0.28.0. Pin last-release-sha to the v0.29.2 release commit (7a53779) so release-please only considers commits after 0.29.2. main is currently exactly at that commit (0 commits after), so on the next run release-please will find nothing to release and close/empty #196. Future releases then bump correctly from 0.29.2. Non-bumping (chore) so this change does not itself trigger a release. The pin can be removed after the next clean release once the tag chain is trusted again. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Closing: this proposes a bogus 0.30.0 that re-lists 168 already-shipped commits (breaking changes released back in v0.28.0) because release-please lost its baseline after the deleted 0.29.1 release. Fixed by #197 (pinned last-release-sha to the v0.29.2 commit). The next release PR — generated once real new commits land (e.g. #198) — will bump correctly from 0.29.2 with only new changes. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
0.30.0 (2026-07-05)
⚠ BREAKING CHANGES
Features
Bug Fixes
Performance Improvements
Documentation
This PR was generated with Release Please. See documentation.