internal: Enable npm trusted publishing #153
Merged
+3
−8
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
This comment has been minimized.
This comment has been minimized.
2Steaks
reviewed
Oct 11, 2025
Contributor
2Steaks
left a comment
2Steaks
left a comment
There was a problem hiding this comment.
Just a zizmor issue to fix, otherwise, code looks good!
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.
We want to harden how packages are published to NPM. We’ll do this by exclusively using NPM Trusted Publishing instead of NPM tokens.
Some pre-work has been done before this PR:
RELEASEhas been created in GitHubThis PR replaces the NPM token and specifies the
RELEASEenvironment during publishing so the release can be trusted by NPM.