You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However the new version is to be managed through corepack. In my opinion the best way forward is to change actions/setup-node@v4 so that it no longer installs yarn globally, but rather enables corepack.#1664 (comment)
Important
This will (theoretically, but I am 99% sure) not impact the rest of the JS repositories, as enabling corepack means that as soon as yarn or pnpm is entered into the command line, corepack installs it (if it isn't already installed), and then executes it. (I'm not sure why, but by default it installs Yarn classic, so it's fine)
Currently this repository is using
yarnclassic.One day, perhaps not too long from now, it will be deprecated for good, it says on the install page.
There are benefits to upgrading.
However the new version is to be managed through corepack.
In my opinion the best way forward is to change#1664 (comment)actions/setup-node@v4so that it no longer installsyarnglobally, but rather enablescorepack.Important
This will (theoretically, but I am 99% sure) not impact the rest of the JS repositories, as enabling
corepackmeans that as soon asyarnorpnpmis entered into the command line,corepackinstalls it (if it isn't already installed), and then executes it. (I'm not sure why, but by default it installs Yarn classic, so it's fine)Read more about upgrading to the latest Yarn:
https://yarnpkg.com/getting-started/install
Migration should be very simple:
https://yarnpkg.com/migration/guide#migration-steps