yarnpkg
Migration to 4.0 is unclear
README > Migration Guide links to "Migrating from 1.x / npm"
It would be helpful to have a guide for upgrading from e.g. 3.x to 4.x, even if it's a brief addition like "Already on a recent version of Yarn? All you need to do is upgrade. Check the changelog to see what's new."
Also adding something like that to the 4.0 blog post might make those users who don't follow the project closely a bit happier.
This is all I had to do to upgrade from v3.
yarn set version berry
yarn install
It was pretty seamless. yarn install will auto-migrate old things it finds.
I want to install yarn 3 only
Wjhat should I do to make this happen from this step
- npm i -g corepack && corepack enable && corepack prepare yarn@stable --activate
- yarn -v
Can some one really help this. this kind of unstable process is troubling us a lot. our pipelines are broken
Can some one really help this. this kind of unstable process is troubling us a lot. our pipelines are broken.
I already answered you in the thread you opened (#5865).
And keep in mind for the future that stable is always the latest stable release (similarly, canary is always the latest release, stable or not). This is a fairly common pattern in software development. If you wish to always use a specific version, then explicitly state you want this specific version.
At least put documentation on the yarn 3 specific installation. thing is how an end user knows you are following this model. of the version bumps
What's so difficult about yarn set version 3.6.3 or corepack prepare [email protected]?
Of course the "stable" tag is always going to point to the latest... stable. Which is v4.
You mean, like, right there?
I don't know why you're trying to take a thread about updating the docs to help users stay on the current version on your sidequest to pin your personal copy to some random version.
You guys think we always have all the time in the world to untangle a mess cause by such a simple command.
