Conversation
Replace yarn set version berry with corepack enable to match packageManager and avoid lockfile v8→v9 migration blocked in PRs. Upgrade actions/setup-node to v4 with yarn cache.
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 73351f9. Configure here.
| - run: yarn set version berry | ||
| cache: yarn | ||
| - name: Enable Corepack | ||
| run: corepack enable |
There was a problem hiding this comment.
Corepack must be enabled before setup-node caching
High Severity
The cache: yarn option in actions/setup-node@v4 runs during the action step and tries to determine the Yarn cache directory. Because corepack enable runs after setup-node, the action uses the system's default Yarn v1.22.x, which conflicts with the "packageManager": "yarn@4.5.0" field in package.json. This is a well-documented issue (actions/setup-node#1027) that causes the CI step to fail. The corepack enable step needs to run before the actions/setup-node@v4 step that uses cache: yarn.
Reviewed by Cursor Bugbot for commit 73351f9. Configure here.
73351f9 to
2cb7436
Compare


Note
Medium Risk
Mostly CI and dependency-lock updates, but the Symfony and assertion library bumps could introduce subtle runtime or tooling behavior changes if the project relies on affected components.
Overview
Updates the GitHub Actions Node workflow by switching to
actions/setup-node@v4, enabling Yarn caching, and explicitly enabling Corepack before installing/building.Refreshes
composer.lockwith newer versions of several PHP dependencies (notablysymfony/*components,phpdocumentor/reflection-docblock, andwebmozart/assert).Applies a no-op formatting/alignment tweak to the
$networksarray ininc/Helpers/Formatting/Share.php.Reviewed by Cursor Bugbot for commit 2cb7436. Bugbot is set up for automated code reviews on this repo. Configure here.