Merged
Conversation
fabracht
added a commit
that referenced
this pull request
Apr 25, 2026
## Summary Cuts `0.4.1` — a republish of `0.4.0` with no source changes. The `0.4.0` tag fired the release workflow but the npm publish step failed before uploading because `--provenance` requires `id-token: write` (fixed in #7). Bumping to `0.4.1` to avoid mutating the existing `v0.4.0` tag. ## Test plan - [x] `npm run check` - [x] `node scripts/extract-changelog.mjs 0.4.1` produces the expected release notes - [x] `package.json` version is `0.4.1` to match the upcoming `v0.4.1` tag ## After merge I'll tag `v0.4.1` at the merge commit and push, which retriggers the publish workflow.
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.
Summary
The
Publish to npmstep inrelease.ymlfailed on the v0.4.0 tag with:The publish command uses
--provenance, which signs the published tarball with an OIDC token issued by GitHub Actions. That requiresid-token: writeon the workflow'spermissionsblock. Adding it.Test plan
permissionsblock grows by one linev0.4.0after merge to trigger a fresh runNotes
Nothing was published to npm in the failed run — the error came before the upload, so the
0.4.0version slot is still available.