fix: Restore semantic-release 0.62.x path and revert mistaken 0.61.0 release on master#6231
Merged
ntkathole merged 4 commits intofeast-dev:masterfrom Apr 8, 2026
Conversation
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
semantic-release uses the latest semver tag ancestor of HEAD. Tag v0.61.0 points at fb2a3bf on v0.61-branch; that commit was never merged to master, so dry-runs proposed 0.61.0 again instead of 0.62.0. Merging v0.61-branch brings the tagged commit into master history.
actions/checkout defaults to shallow clones; semantic-release needs full git history to analyze commits since the last tag. Signed-off-by: ntkathole <nikhilkathole2683@gmail.com> Made-with: Cursor
This reverts commit b374396.
franciscojavierarceo
approved these changes
Apr 7, 2026
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
2 participants
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.
What this PR does / why we need it:
semantic-release dry-runs on master proposed 0.61.0 again instead of 0.62.0 because the v0.61.0 tag points at fb2a3bf on v0.61-branch, which was not an ancestor of master.
What this PR does
b374396aeto drop the mistaken duplicate chore(release): release 0.61.0 churn (notably the extra CHANGELOG.md section and operator bundle / e2e binary updates from that run).