Repository navigation
chore(release): undo the 4.0.0 release commit so it can run again - #112
Merged
Merged
Conversation
The 4.0.0 release pushed its commit and tag, then npm publish failed with TLOG_CREATE_ENTRY_ERROR: the Sigstore transparency log returned a 500 while npm was recording the provenance attestation, so nothing reached npm and no GitHub release was created. Re-running the job cannot recover from that, because main is already ahead of the commit the job checked out. This puts CHANGELOG.md, package.json, package-lock.json and the skill file back to 3.10.0, so the next release run writes the 4.0.0 entry once instead of adding a second copy above the first.
doistbot
reviewed
Nov 7, 2026
doistbot
left a comment
Member
There was a problem hiding this comment.
This PR updates chore(release): undo the 4.0.0 release commit so it can run again. No issues were flagged in the reviewed diff.
Contributor
|
🎉 This PR is included in version 4.0.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
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.
The 4.0.0 release (run) pushed its release commit and the
v4.0.0tag, thennpm publishfailed withTLOG_CREATE_ENTRY_ERROR: the Sigstore transparency log returned a 500 while npm was recording the provenance attestation. Nothing reached npm (latest is still 3.10.0) and no GitHub release was created. todoist-cli failed the same way at the same time.Re-running the job can't recover from this. semantic-release checks out the commit that triggered the run, and main is now ahead of it because of the release commit, so it logs "behind the remote" and exits without publishing.
This reverts the release commit, putting
CHANGELOG.md,package.json,package-lock.jsonandskills/comms-cli/SKILL.mdback to 3.10.0. Before this merges, thev4.0.0tag and itsrefs/notes/semantic-release-v4.0.0note are deleted, so merging triggers a fresh release run that finds 3.10.0 as the last release, works out 4.0.0 again and writes its changelog entry once.Verification
npm run verifypasses locally.