Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix CI Error: Yarn Version Mismatch
Resolves CI failures after merging to main where workflows failed with:
Key Changes
Updated all GitHub Actions workflows to use
[email protected](matchingpackage.json) via Corepack:.github/workflows/prod.yml- Addedcorepack prepare [email protected] --activateto properly set up Yarn before Vercel commands.github/workflows/build.yml- Updated from[email protected]to[email protected].github/workflows/pr.yml- Updated from[email protected]to[email protected].github/workflows/playwright-visual-regression.yml- Updated from[email protected]to[email protected]Root Cause
The project's
package.jsonspecifies"packageManager": "[email protected]", which requires Corepack to be enabled with that exact version. The CI workflows were either:[email protected])This caused Corepack to reject the version mismatch and fail the build.
Solution
All workflows now explicitly activate
[email protected]using:This ensures consistent dependency management across all CI environments and matches the version declared in
package.json.Testing
package.jsonspecificationBackward Compatibility
✅ 100% backward compatible - This change only affects CI/CD environments, not runtime behavior. All workflows will now use the correct Yarn version as specified in
package.json.