Skip to content

ci: use npm to publish directly rather than yarn #2613

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Aug 5, 2025

Conversation

Saadnajmi
Copy link
Collaborator

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.

Copy link
Member

@tido64 tido64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title and the change don't match. Otherwise it looks fine to me.

@Saadnajmi
Copy link
Collaborator Author

The title and the change don't match. Otherwise it looks fine to me.

Actually yes, the var should be false. Updating

@Saadnajmi Saadnajmi merged commit 20c4bd4 into microsoft:main Aug 5, 2025
21 checks passed
@Saadnajmi Saadnajmi deleted the myfix branch August 5, 2025 05:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

yarn ./packages/virtualized-lists npm publish fails authentication
2 participants