Repository navigation
chore(hoolicy): recover unpublished release preparation - #37
Merged
Merged
Conversation
wakemeup0
enabled auto-merge (squash)
October 3, 2026 19:34
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
1 participant
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.
Recover unpublished v0.4.1 preparation
The first release PR was squash-merged with a replacement subject/body, which prevented Hooversion 1.1.1 from recognizing the prepared release. Its attempted direct version bump was rejected atomically by branch protection; no release or tag was published.
After this PR passes CI and merges, the normal Hooversion prepare workflow will regenerate v0.4.1. The next release PR will retain the prepared subject and body exactly during squash merge.