-
Notifications
You must be signed in to change notification settings - Fork 1
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
Workspaces are not correctly handled in yarn v4 #210
Labels
Comments
hongaar
added a commit
that referenced
this issue
Oct 29, 2023
Add previously default `--worktree` to `yarn workspaces foreach` commands. Fixes #210
🎉 This issue has been resolved in version 3.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Thanks for reporting this ShauniArima, this should now be fixed with the above release ⬆️ Edit: @ShauniArima I see your edit now 😄 I will make another PR to change |
Thank you! 🙂 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
workspaces
with yarn v4 does not work as--all
,--recursive
or--worktree
argument is mandatory now.Link to the changelog of
yarn 4
: https://yarnpkg.com/advanced/changelog#major-changesExample of stacktrace:
I will suggest to use
--worktree
as it was the default value in v3 ^^Edit: after some tests it seems that
--worktree
doesn't exist in v3. Should we use--all
or another argument to avoid checking yarn's version?The text was updated successfully, but these errors were encountered: