Configure trusted publishing#1202
Merged
ecraig12345 merged 2 commits intomainfrom Apr 10, 2026
Merged
Conversation
ecraig12345
force-pushed
the
trusted-publishing
branch
from
6a448d1 to
7ba0158
Compare
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
1 participant
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.
Run release build on newer Node/npm and configure trusted publishing.
Run PR builds on newer Node/npm in addition to old. For now I had to use Node 20 (not 22) because with verdaccio 5, the
npm loginrequest to the mock registry fails for unknown reasons. This works fine in latest verdaccio, but it's not possible to upgrade yet due to incompatibilities with old Node/npm.