Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Upgrade to yarn v4 with yarnPath #8

Merged
merged 3 commits into from
Nov 29, 2023
Merged

Upgrade to yarn v4 with yarnPath #8

merged 3 commits into from
Nov 29, 2023

Commits on Nov 20, 2023

  1. Upgrade to yarn v4 with corepack 

    Specifies the package manager (yarn) and version (4.0.2) in package.json. The package-lock.json file was removed. Yarn reported an error due to having both it and yarn.lock. There should only be one lock file. The yarn.lock file has been rewritten in the latest yarn lock format.
    @shakuzen
    shakuzen committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    7bb69a5 View commit details
    Browse the repository at this point in the history

  2. Check in yarn locally to workaround setup-node 

    The original intent was to use yarn v4 via corepack as is encouraged, but the setup-node action does not have an option to enable corepack.
We can check in yarn to source control and use that copy until corepack is more easily usable with setup-node.
    @shakuzen
    shakuzen committed Nov 20, 2023
    Configuration menu
    Copy the full SHA
    e706a34 View commit details
    Browse the repository at this point in the history

  3. Merge branch 'main' into corepack-yarn4

    @shakuzen
    shakuzen authored Nov 20, 2023
    Configuration menu
    Copy the full SHA
    dae02ba View commit details
    Browse the repository at this point in the history