chore(release): revert the half-published 5.7.0 release commit - #71
Merged
Conversation
The master release for #68 ran three times. Attempt 2 got through prepare, pushing this release commit and tag v5.7.0, then `npm publish` failed with EOTP because the npm token still required a one-time password. Attempt 3 checked out the original merge SHA, saw master behind, and exited green without publishing. So 5.7.0 exists in CHANGELOG.md and package.json but not on npm or GitHub releases, and the tag made semantic-release consider it already released. The tag has been deleted. Reverting the release commit lets the next master run cut 5.7.0 properly: changelog, version, tag, npm, GitHub release and the beta backmerge, from the same two commits (the #68 merge and its feat). This reverts commit a0fe40a. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xa9BAPFheAQLJwta16v67z
|
🎉 This PR is included in version 5.7.0 🎉 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
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.
Why
The master release for #68 never reached npm. The run had three attempts:
verifyConditionsfailed: invalid npm token (issue The automated release is failing 🚨 #70).preparepushed release commit a0fe40a and tagv5.7.0;npm publishthen failed withEOTP(the token still required a one-time password).The 4.x release (#69 → v4.12.0) at 00:01 published fine, so the token is now automation-grade. But with tag
v5.7.0sitting on a0fe40a, semantic-release sees nothing to release on master.What
v5.7.0has been deleted from the remote (nothing on npm or GitHub releases referenced it).Merging it triggers a fresh master run: the commits since
v5.6.0are the #68 merge, itsfeat(routing), the release commit and this revert, so semantic-release will cut 5.7.0 cleanly — changelog, version bump, tag, npm publish, GitHub release, and the backmerge tobeta— with no duplicate changelog section.🤖 Generated with Claude Code
https://claude.ai/code/session_01Xa9BAPFheAQLJwta16v67z