fix: publish through npx npm@11 with an explicit dist-tag - #53
Merged
Merged
Conversation
The tag-triggered publish failed on npm 11's new prerelease guard: "You must specify a tag using --tag when publishing a prerelease version." Publish via `npx npm@11` with an explicit `--tag latest` (the beta deliberately lands on `latest`), mirroring the working logto-io/cli-auth setup: the npx pin also removes the dependency on the Node-bundled npm version, so the publish job goes back to Node 22 in line with the rest of CI. Also normalize `repository.url` to the `git+https` form npm 11 auto-corrects at publish time. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
simeng-li
approved these changes
Aug 31, 2026
charIeszhao
approved these changes
Aug 31, 2026
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
3 participants
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.
Root cause of the failed tag publish
The
v1.0.0-beta.1run died on a client-side guard new in npm 11:Moving the publish job to Node 24 (#52) gave the delegated npm CLI its OIDC capability (npm ≥ 11.5.1) — and along with it npm 11's prerelease protection, which refuses to publish a
-betaversion without an explicit--tag. Reproduced locally withnpx npm@11 publish --dry-run; adding--tag latestmakes the same dry-run pass cleanly. OIDC itself was not the failure point.Changes
npx --yes npm@11 publish --tag latest --provenance, mirroring the working logto-io/cli-auth setup: the npx pin removes the dependency on the Node-bundled npm (so the job returns to Node 22, in line with the rest of CI), and the explicit--tag latestsatisfies npm 11's prerelease guard while implementing this package's deliberate publish-betas-to-latestpolicy.repository.urltogit+https://…— the form npm 11 auto-corrects (with a warning) at publish time.Verified:
npx npm@11 publish --dry-run --tag latestcompletes cleanly frompackages/mcp-auth(also confirming the rootdevEnginesguard does not block delegated npm publishes).After merge: re-point
v1.0.0-beta.1at the merge commit and push it to trigger the publish.🤖 Generated with Claude Code