Download link is not working

[jessejiang0214]

The link which downloads the latest version of Yarn 1.0x is not working
https://yarnpkg.com/latest.msi
https://github.com/yarnpkg/yarn/releases/download/v1.22.13/yarn-1.22.13.msi

[arcanis]

ping @Daniel15 - I guess this is related to the Windows CI not running anymore?

[codebarz]

Any update on this? This link https://yarnpkg.com/downloads/1.22.10/yarn-v1.22.10.tar.gz. is also not working on Netlify. @jessejiang0214, where you able to fix the issue?

[brancz]

Same for https://yarnpkg.com/downloads/1.22.4/yarn-v1.22.4.tar.gz on netlify

[erezrokah]

Hi all 👋 , Erez from Netlify here, we've posted an update on our status page https://www.netlifystatus.com/incidents/l6rk7f1hqfd7

[arcanis]

@erezrokah do you have some details? Did something break in Yarn's infra, or is it just something from Netlify's one?

(Note that the initial issue in the OP is about msi builds, nothing to do with the tgz tarballs or ssh)

[Daniel15]

ping @Daniel15 - I guess this is related to the Windows CI not running anymore?

Hmm it should still work as there's bits I haven't shut down yet. My guess would be that the system we use for Windows builds (AppVeyor?) failed. If all else fails I can manually build it.

[Daniel15]

@arcanis Looks like the build failed: https://ci.appveyor.com/project/kittens/yarn/builds/40963544. I'll just manually build it myself.

[erezrokah]

@erezrokah do you have some details? Did something break in Yarn's infra, or is it just something from Netlify's one?

The Netlify failures are a separate issue related to Netlify's infra and specific build images. We'll post another update soon.

[Daniel15]

I've manually built an MSI installer, signed it with our Authenticode cert, and attached it to the most recent release. https://classic.yarnpkg.com/latest.msi URL works now, and installs successfully.

PS C:\Users\danlo> yarn --version
1.22.15

Build commands, for reference:

yarn install --frozen-lockfile
& 'C:\Program Files\Git\bin\bash.exe' ./scripts/build-dist.sh
yarn run build-win-installer

then signed with DigiCert Certificate Utility.

@arcanis Please feel free to ping me if that's needed for future releases too :)

Since that's now fixed, and that was the original issue in the OP, I'm going to close this issue. The Netlify issue is a separate issue and you should follow up with Netlify's team for updates on that (since the Yarn team members unfortunately can't help with things that are at Netlify's end)

[ehmicky]

A fix has been implemented for Netlify users. The mitigation is automatic on Xenial, but Trusty sites will have to update to Xenial or Focal in order to mitigate.

We'll continue to monitor for a while before resolving the incident. We will post additional updates on the Netlify status page.

[Haroenv]

Could this be related to the issue I'm seeing here: algolia/vue-instantsearch#1067 (curl: (60) SSL certificate problem: certificate has expired for curl -o- -L https://yarnpkg.com/install.sh | bash -s -- --version 1.13.0)

[ehmicky]

This might be related. Many providers and projects have been experiencing issues since yesterday due to Let's Encrypt root certificate expiry.

[JakeThurman]

This issue should be reopened.

https://yarnpkg.com/latest.msi is broken again since the current version does not have an msi. It seems that most of the recent releases do not. Just scanning down https://github.com/yarnpkg/yarn/releases:

• v1.22.17 does not have an msi
• v1.22.16 does not have an msi
• v1.22.15 does have an msi
• v1.22.14 does not have an msi
• v1.22.13 does not have an msi
• v1.22.12 does not have an msi
• v1.22.11 does not have an msi
• 1.22.10 does not have an msi
• v1.22.5 does have an msi
• v1.22.4 does have an msi
• v1.22.3 does have an msi
• v1.22.2 does not have an msi
• v1.22.1 does have an msi
• v1.22.0 does have an msi

It seems that this may just be an oft forgotten step of the release process.
If every release is not going to have an msi, it would nice if yarn at least didn't tell you to upgrade using a dead link 😳

[AyoCodess]

i'm having this issue now too