A recent commit upgraded the version of Yarn to v4 and removed the Yarn binary from the repo, thereby requiring that Corepack be installed in order to install dependencies. The build-lint-test was updated to install Corepack, but not the documentation-related workflows, so they are failing.
This commit fixes those workflows to install Corepack. It also cleans up some work that was done in previous commits:
In the build-lint-test workflow we ensure that prepare is run once per Node version we are testing and that build and lint use the latest Node version we are testing.
In steps where we are installing Node just to gain access to the corepack executable, we use .nvmrc (the version of Node we use for development) to know which version of Node to install rather than using the latest LTS (lts/*). For jobs that do not need to concern themselves with being run in multiple Node versions, this ensures that consistent Node versions are used in this step vs. the step that is used to simply restore the Yarn cache.
The checkout step always goes first, this way .nvmrc can be read.
A recent commit upgraded the version of Yarn to v4 and removed the Yarn binary from the repo, thereby requiring that Corepack be installed in order to install dependencies. The
build-lint-testwas updated to install Corepack, but not the documentation-related workflows, so they are failing.This commit fixes those workflows to install Corepack. It also cleans up some work that was done in previous commits:
build-lint-testworkflow we ensure thatprepareis run once per Node version we are testing and thatbuildandlintuse the latest Node version we are testing.corepackexecutable, we use.nvmrc(the version of Node we use for development) to know which version of Node to install rather than using the latest LTS (lts/*). For jobs that do not need to concern themselves with being run in multiple Node versions, this ensures that consistent Node versions are used in this step vs. the step that is used to simply restore the Yarn cache..nvmrccan be read.