switch to trusted publishing for npmjs.com #34
Merged
Conversation
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
pavelkornev
reviewed
Aug 20, 2025
Contributor
Author
|
FYI: The If you want to publish a new version you must use trusted publising. |
pavelkornev
approved these changes
Jan 5, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This Pull Request updates the release workflow to utilize npmjs.com's trusted publishing.
As trusted publishing requires npm CLI version
>=11.5.1, we manually install the latest version since the default installed npm version is insufficient.This change eliminates the need for a static
NPM_TOKENsecret, instead using short-lived OIDC identity tokens for authentication and package upload.The necessary setup on npmjs.com has already been completed.
After this pull request is merged I will remove and invalidate the current static
NPM_TOKENsecret.