This is an enhancement request to add examples to clearly demonstrate using GHA for both Yarn 1 (Classic) and Yarn Berry / Modern (Version 2 and later).

Current situation

The following workflows and example directories target yarn:

• .github/workflows/example-install-command.yml using

  • examples/install-command with the corresponding v9 version, both with a yarn.lock lockfile v1.

• .github/workflows/example-start-and-yarn-workspaces.yml using

  • examples/start-and-yarn-workspaces including two workspaces, with a corresponding v9 version, both with a yarn.lock lockfile v1.

The examples demonstrate only Yarn 1 (Classic).

Suggestion

Create new workflows with yarn in their names so that they are easily identified:
- Yarn 1 (Classic) example-yarn-classic
- Yarn Modern example-yarn-modern

Naming

Note that both terms Yarn Berry and Yarn Modern are in use and equivalent.

The GitHub repository https://github.com/yarnpkg/berry is named with the term berry. It includes releases for Yarn version 2 onwards. The site https://yarnpkg.com/ includes the note "This documentation covers modern versions of Yarn.", introducing the term "modern". The page https://yarnpkg.com/getting-started/qa#why-should-you-upgrade-to-yarn-modern more specifically uses the terms Yarn Classic and Yarn Modern side-by-side when discussing migration.

I suggest to use the term Yarn Modern, when referring to Yarn version 2 and later, in preference to the term Yarn Berry. The term Yarn Modern is immediately recognizable as being a later version than Yarn Classic without the need for any reference materials.

Related documentation issue

• Documentation for usage with Yarn Berry / Modern (Version 2 and later) #798