ci: Use Trusted Publishing#54
Merged
Merged
Conversation
alexgerardojacinto
approved these changes
Oct 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
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.
Description
Use Trusted Publishing to npm, to stop dependending on specific npm tokens.
Needed to update
semantic-releaseto the latest version to support Trusted Publishing. Also needed to update node version and guarantee recent npm cli version.Also removed lerna from this repository, since we're not using it.
This PR is open to main, but once it's merged we should merge
mainwithnextto also be configured with trusted publishing, and after that we can safely remove the npm token secret from this repo.Context