Yarn nightly reverted to 1.22 - version yarn classic fallback for git dependencies?

[devshorts]

It seems that yarn nightly yesterday was at

 YN0000: │ /private/var/folders/11/nh0v1jld7zd7b9zqm1774gtm0000gn/T/xfs-35f3355e STDOUT ➤ YN0000: Retrieving https://nightly.yarnpkg.com/latest.js
➤ YN0000: │ /private/var/folders/11/nh0v1jld7zd7b9zqm1774gtm0000gn/T/xfs-35f3355e STDOUT ➤ YN0000: Saving the new release in .yarn/releases/yarn-1.23.0-20220130.1630.cjs

and today it's at

➤ YN0000: │ /private/var/folders/11/nh0v1jld7zd7b9zqm1774gtm0000gn/T/xfs-caf1d7a9 STDOUT ➤ YN0000: Retrieving https://nightly.yarnpkg.com/latest.js
➤ YN0000: │ /private/var/folders/11/nh0v1jld7zd7b9zqm1774gtm0000gn/T/xfs-caf1d7a9 STDOUT ➤ YN0000: Saving the new release in .yarn/releases/yarn-1.22.19.cjs

For packages that are dependent on git repos which are still on yarn classic, is it possible to pre-version the classic yarn runner such that we don't need to make an over the wire call for nightly? I'm finding that for some reason a package is not compiling under 1.22 but worked fine with 1.23

[arcanis]

The 1.x nightlies aren't built anymore. Hotfixes we publish are on the 1.22 branch, not master, so nightlies were actually lagging behind.

Given how rarely we make changes to 1.x nowadays, for all intent and purposes, the nightlies have been set to be equivalent with the latest stable.

[TasukuUno]

For packages that are dependent on git repos which are still on yarn classic, is it possible to pre-version the classic yarn runner such that we don't need to make an over the wire call for nightly? I'm finding that for some reason a package is not compiling under 1.22 but worked fine with 1.23

I have the exact same issue. Now I can not install with error The remote archive doesn't match the expected checksum and I think it is because the version installed via https://nightly.yarnpkg.com/latest.js changed.

@arcanis Is it inevitable that the version of https://nightly.yarnpkg.com/latest.js is used in git root directory? I hope there are any workarounds... Or what we end-users can do are:

• update to berry in all of git dependencies
• quit using git URL
• YARN_CHECKSUM_BEHAVIOR=ignore