chore(cli): limit yarn@^1.0.0

[erickzhao]

Explicitly disallows Yarn 2 and drops support for Yarn 0.x.

This is technically a breaking change, but according to npm's download stats, Yarn 0.x only has 2000 installs (~0.08%) of yarn (<=1.x) installs in the last week.

[mahnunchik]

@erickzhao could you please assist how to install deps and build the project? Current yarn produces 1+ changes in the sources on install command.

I'd like to rebase and move forward the changes I need for the production project:

• feat(publisher-gcs): add Google Cloud Storage publisher #2100
• feat(publisher-github): assets management #1761

[mahnunchik]

What is the purpose to use yarn instead of npm?

[erickzhao]

could you please assist how to install deps and build the project? Current yarn produces 1+ changes in the sources on install command.

Which yarn version are you using? I ran a clean install on my machine this week and there are no changes on install for me.

[mahnunchik]

I used system version after corepack enable. It was 3.2.4 and it produces 1K+ changes in the sources.

After I've switched to 1.22.19 via yarn set version 1.22.19 but there are still changes: new .yarnrc.yml file, .yarn folder and field in package.json.

I was able to figure out that changes and not submit with PR.

[erickzhao]

This would fix it but I'm not sure what other maintainers think about the corepack thing: #3359

[adidahiya]

Why is Yarn v4.x disallowed? It was working fine for me with the classic nodeLinker: node-modules install mode with electron-forge v6.x.

[erickzhao]

reversing course here @adidahiya #3411