chore: publish to npm with OIDC#5912
Merged
KazariEX merged 1 commit intovuejs:masterfrom Jan 25, 2026
Merged
Conversation
KazariEX
approved these changes
Dec 28, 2025
xiaoxiangmoe
approved these changes
Dec 28, 2025
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.
update the release to publish to npm with OIDC, Lerna-Lite (which I maintain) supports OIDC. Publishing with OIDC has multiple advantages, it publishes with Provenance, it also uses short lived token which is also much better for security and finally you no longer need an npm token.
Please note that you will also have to enable Trusted Published for each package of the monorepo, for example below is one of Lerna-Lite package.
For more info, see e18e/ecosystem-issues#201
Please don't merge this PR unless you have already updated each package to use Trusted Published as shown below. I assume that you could give it a try with
--dry-runmode to test it out afterward.