fix: re-release after revert of PR #89#94
Merged
Conversation
The revert in PR #93 used GitHub's default revert UI, which produced a commit message of `Revert "feat: ..."` without a `revert:` prefix or `This reverts commit <hash>.` footer. semantic-release's commit-analyzer therefore skipped the commit ("The commit should not trigger a release") and no version was published, leaving the reverted code unreleased on npm. This empty commit re-triggers semantic-release so the revert ships as a patch release.
samblacklock
approved these changes
May 13, 2026
|
🎉 This PR is included in version 34.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
No description provided.