Skip to content

chore(release): undo the 4.0.0 release commit so it can run again - #112

Merged
scottlovegrove merged 1 commit into
mainfrom
chore/retry-4.0.0-release
Nov 7, 2026
Merged

scottlovegrove merged 1 commit into
mainfrom
chore/retry-4.0.0-release

Conversation

@scottlovegrove

Copy link
Copy Markdown
Collaborator

The 4.0.0 release (run) pushed its release commit and the v4.0.0 tag, then npm publish failed with TLOG_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.json and skills/comms-cli/SKILL.md back to 3.10.0. Before this merges, the v4.0.0 tag and its refs/notes/semantic-release-v4.0.0 note 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 verify passes locally.
  • Once merged, the release run should publish 4.0.0 to npm and create the GitHub release.

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.
@scottlovegrove scottlovegrove self-assigned this Nov 7, 2026
@scottlovegrove scottlovegrove added the 🚢 Ship PR requires passing checks before merge, but no independent human review. label Nov 7, 2026

@doistbot doistbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Share Feedback • Review Logs

@scottlovegrove
scottlovegrove merged commit ba1b852 into main Nov 7, 2026
6 checks passed
@scottlovegrove
scottlovegrove deleted the chore/retry-4.0.0-release branch November 7, 2026 17:56
@doist-release-bot

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 4.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

released 🚢 Ship PR requires passing checks before merge, but no independent human review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants