-
Notifications
You must be signed in to change notification settings - Fork 359
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Examples for Yarn 1 (Classic) and Yarn Berry / Modern (Version 2 and later) #799
Labels
type: feature
feature request
Comments
Assuming agreement, I plan to submit a PR to implement this enhancement request. |
I've been reviewing my suggestion and I plan to split it into two parts:
otherwise it will be unduly complex and difficult to review. |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
yarn.lock
lockfile v1..github/workflows/example-start-and-yarn-workspaces.yml using
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
andYarn 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 termsYarn Classic
andYarn 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 termYarn Berry
. The termYarn Modern
is immediately recognizable as being a later version thanYarn Classic
without the need for any reference materials.Related documentation issue
The text was updated successfully, but these errors were encountered: