Skip to content
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

chore: don't constrain yarn releases we mirror #3258

Closed
wants to merge 1 commit into from
Closed

Conversation

alexeagle
Copy link
Collaborator

fixes #3071

@alexeagle alexeagle closed this Jan 17, 2022
@alexeagle alexeagle reopened this May 5, 2022
@alexeagle alexeagle changed the base branch from 5.x to stable May 5, 2022 15:21
@alexeagle
Copy link
Collaborator Author

This doesn't actually work.
Yarn 2 berry seems to put the release artifacts somewhere else, https://registry.npmjs.org/yarn doesn't have them. Will need someone with more resources to contribute a fix here.
I'd also note that I think pnpm is the most promising package manager to use with Bazel, and so I'm not planning to keep working on this myself.

@alexeagle alexeagle closed this May 5, 2022
@alexeagle alexeagle deleted the i3071 branch August 10, 2022 21:45
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_versions helper only includes v1
1 participant