-
Notifications
You must be signed in to change notification settings - Fork 11
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
yarn@4.0.0-rc.26
is not within ranage for >=1.22.0
#10
Comments
We use the |
I see! Feel free to close this issue if you think that the current behavior is correct. I’m happy both ways. |
I'll think about this a bit and then post back the final decision :) |
By default, the `semver` library excludes prerelease check unless explicitly included in the range: https://github.com/npm/node-semver#prerelease-tags. This behavior is handy for the wide range of npm packages where their authors can publish any versions breaking SemVer rules and those version will be picked up by ranges specified by users and installed breaking application. For the purpose of this plugin, we only deal with two mature projects and check that version matches the range specified by the user, but never install/update this version. If the user chose the `>X.Y.Z` constraint, we assume that they know what they are doing and choose less surprising SemVer range checking behavior. Fixes #10
By default, the `semver` library excludes prerelease check unless explicitly included in the range: https://github.com/npm/node-semver#prerelease-tags. This behavior is handy for the wide range of npm packages where their authors can publish any versions breaking SemVer rules and those version will be picked up by ranges specified by users and installed breaking application. For the purpose of this plugin, we only deal with two mature projects and check that version matches the range specified by the user, but never install/update this version. If the user chose the `>X.Y.Z` constraint, we assume that they know what they are doing and choose less surprising SemVer range checking behavior. Fixes #10
Hi @devoto13! 👋 Thanks for this handy plugin! 💯
I just bumped Yarn from v3 to v4 RC using
yarn set version canary
:Running
yarn install
produced this:Replacing
"yarn": ">=1.22.0"
with"yarn": ">=1.22.0 || ^4.0.0-rc"
works but I wonder if this is expected behavior. WDYT?The text was updated successfully, but these errors were encountered: