ci: use npm to publish directly rather than yarn #2613
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
This was referenced Aug 3, 2025
tido64
approved these changes
Aug 4, 2025
Member
tido64
left a comment
tido64
left a comment
There was a problem hiding this comment.
The title and the change don't match. Otherwise it looks fine to me.
Collaborator
Author
Actually yes, the var should be false. Updating |
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.
Summary:
Fixes #2612 . Add a variable to switch between using Yarn or NPM to publish. Long term we should wait till Yarn publish fix (yarnpkg/berry#6850) is integrated into NX, and then move to the nx release programmatic API.