Skip to content

Fixes actions issues#487

Closed
firestar300 wants to merge 3 commits intomasterfrom
chore/actions-issues
Closed

Fixes actions issues#487
firestar300 wants to merge 3 commits intomasterfrom
chore/actions-issues

Conversation

@firestar300
Copy link
Copy Markdown
Contributor

@firestar300 firestar300 commented Apr 24, 2026

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.lock with newer versions of several PHP dependencies (notably symfony/* components, phpdocumentor/reflection-docblock, and webmozart/assert).

Applies a no-op formatting/alignment tweak to the $networks array in inc/Helpers/Formatting/Share.php.

Reviewed by Cursor Bugbot for commit 2cb7436. Bugbot is set up for automated code reviews on this repo. Configure here.

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.
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ 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
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 73351f9. Configure here.

@firestar300 firestar300 force-pushed the chore/actions-issues branch from 73351f9 to 2cb7436 Compare April 24, 2026 10:15
@firestar300 firestar300 deleted the chore/actions-issues branch April 24, 2026 13: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.

1 participant