Repository navigation
Release through npm staged publishing; bump to 1.0.0-alpha.2 - #54
Merged
jallers merged 2 commits intoNov 11, 2026
Merged
Conversation
publish.yml now runs `npm stage publish`, so a tagged release lands in the registry uninstallable until a maintainer approves it with 2FA (`npm stage approve <stage-id>` or on npmjs). The stage ID and the approve/reject commands go to the run's summary. npm 11.15.0 is the first release with `npm stage`. The trusted-publisher link on npmjs grants only `npm stage publish` (and `npm dist-tag`), as npm recommends, which is why the direct `npm publish` of v1.0.0-alpha.1 failed with ENEEDAUTH. The README's Releasing section describes the approval step and the expiring link. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016NSWj8mSZ8LrMj16R2cozL
1.0.0-alpha.1 was tagged but never published: its workflow ran a plain npm publish, which the trusted-publisher link does not allow. The next release goes out through npm stage publish as 1.0.0-alpha.2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016NSWj8mSZ8LrMj16R2cozL
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.
Why
The
v1.0.0-alpha.1publish run failed withENEEDAUTH. The npm trusted-publisher link for this repository grants only npm stage publish and npm dist-tag, which is what npm recommends, so the workflow's plainnpm publishwas never allowed. (The link had also expired; it has since been recreated and shows as valid.)Changes
.github/workflows/publish.ymlnpm stage publish --provenance --access public --tag <dist-tag>instead ofnpm publish. A tagged release now sits in the registry uninstallable until a maintainer approves it with 2FA.npm stage view/approve/rejectcommands. If the stage ID can't be parsed from the output, the summary says to usenpm stage list.^11.15.0, the first release that hasnpm stage(11.14.0 doesn't).ENEEDAUTH).1.0.0-alpha.2. alpha.1 was tagged but never published. Its tag points at the old workflow, so we're releasing a new version rather than moving that tag.npm run verifypasses (19 files, 131 tests). I couldn't run the stage step itself outside a tagged run. The line that extracts the stage ID matches npm's+ <pkg>@<version> (staged with id <id>)output (lib/commands/publish.jsin npm 12.2.2).Releasing after merge
git tag v1.0.0-alpha.2 <merge-sha> && git push origin v1.0.0-alpha.2npmenvironment on the Publish run.npm stage approve <stage-id>(2FA), or on the package's npmjs page.Generated by Claude Code