Skip to content

fix: run yarn install in correct working directory with Yarn v4 support - #31

Draft
Kushmanmb with Copilot wants to merge 2 commits into
mainfrom
copilot/yarn-install-dependencies
Draft

fix: run yarn install in correct working directory with Yarn v4 support#31
Kushmanmb with Copilot wants to merge 2 commits into
mainfrom
copilot/yarn-install-dependencies

Conversation

Copilot AI commented Mar 24, 2026

Copy link
Copy Markdown

The CI workflow was running yarn install and yarn test from the repo root, which has no package.json. Yarn v1 was silently succeeding (creating an empty lockfile), then yarn test failed hard. Corepack was never enabled, so Yarn v4 Berry (declared in packageManager) was never activated.

Changes

  • Working directory: Set defaults.run.working-directory: app so all steps run where package.json and yarn.lock actually live
  • Corepack: Added corepack enable step (scoped to workspace root since it's a global operation) to activate Yarn v4 Berry
  • Yarn cache: Added cache: 'yarn' with cache-dependency-path: 'app/yarn.lock' pointing at the correct lockfile
  • Install flags: Changed yarn installyarn install --immutable to prevent lockfile mutations in CI
  • Test step: Replaced yarn test (no such script) with yarn lint (defined in package.json)
Original prompt

Yarn install


🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.

Copilot AI changed the title [WIP] Add yarn install for managing project dependencies fix: run yarn install in correct working directory with Yarn v4 support Mar 24, 2026
Copilot AI requested a review from Kushmanmb March 24, 2026 03:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants