Update Yarn to latest version

[sPaCeMoNk3yIam]

Problem

Currently the docker image for node 16 has yarn hardcoded at v 1.22.5. This version is already a year old and yarn has seen some bugfixes since then.

Solution

It would be great to keep track of yarn releases and apply them, when found to be flawless.

Alternatives to Consider

Of course, I can upgrade yarn when building the container but that seems not to be a solid solution.

[nschonni]

https://classic.yarnpkg.com/latest-version 1.22.5 is the latest v1 version of yarn.
See #1180 for discussion on v2

[sPaCeMoNk3yIam]

https://classic.yarnpkg.com/latest-version 1.22.5 is the latest v1 version of yarn.
See #1180 for discussion on v2

I was actually referencing to Yarn v1: https://github.com/yarnpkg/yarn/releases/tag/v1.22.11
https://github.com/yarnpkg/yarn/releases/
Seems like the above link (latest-version) is not reliable. Also, in the landing page they give the wrong version number, when you click on it and get directed to the changelog on Github, oc again 1.22.11.

I'm asking about it, because when updating or freshly installing yarn... you know the deal.

[SimenB]

If it was unclear: we install the version https://classic.yarnpkg.com/latest-version returns - whenever that is updated the docker images for the next node release will contain the updated version. So as long as that receives an update, a new version of yarn will tickle through with no changes in this repo

[sPaCeMoNk3yIam]

If it was unclear: we install the version https://classic.yarnpkg.com/latest-version returns - whenever that is updated the docker images for the next node release will contain the updated version. So as long as that receives an update, a new version of yarn will tickle through with no changes in this repo

Yes, I thought so, that's why I opened an issue on Yarn's side as well. I wonder if that address is still supported or if there's another/new way of getting the latest release of yarn classic. At least it doesn't update automatically according to the releases that are published and installed, when installing yarn. Anyways, will see how this progresses now...

[SimenB]

@arcanis ^

[arcanis]

The v1 release pipeline broke last year, so I had to do the last few releases manually, which caused some delta in the versions listed on the website vs what's on npm. I'll book some time to address that.

[arcanis]

The website is now updated to reflect 1.22.13

[SimenB]

Thanks!

[nschonni]

FYI, tests look OK #1571 but the actual bump will happen the next time each of the versions is bumped

[arcanis]

Note that we released 1.22.15 to address a couple of issues around bin script execution. Feel free to ping me next time you bump Yarn, just in case!

[SimenB]

It'll be bumped the next time Node makes a release. I can try to remember to ping you, but in general just watching https://nodejs.org/en/blog/ then checking this repo a few hours later (as we need to wait for the MUSL build) should let you follow it 🙂

We have a smoke test for Yarn (yarn --version), but that doesn't catch anything except it not being on $PATH.