Skip to content

[Snyk] Security upgrade lerna from 3.0.0-rc.0 to 6.4.1 #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MHxGH-ServiceAccount wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade lerna from 3.0.0-rc.0 to 6.4.1 #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@
]
},
"dependencies": {
"lerna": "^3.0.0-rc.0"
"lerna": "^6.4.1"

@cursor cursor Bot Mar 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lerna 6 upgrade breaks release-canary script flags

High Severity

Upgrading lerna to ^6.4.1 breaks the release-canary script, which uses --cd-version and --npm-tag flags that were removed/renamed in lerna v6. The --cd-version flag was replaced by a positional argument to lerna version, and --npm-tag was renamed to --dist-tag. The canary release workflow will fail at runtime with unrecognized option errors.

Fix in Cursor Fix in Web

@cursor cursor Bot Mar 12, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lockfile not updated, security fix not applied

High Severity

The package.json declares lerna@^6.4.1 but the yarn.lock still resolves lerna@^3.0.0-rc.0 to version 3.0.0-rc.0. This means the security vulnerability (SNYK-JS-TAR-15456201) that this PR aims to fix won't actually be remediated. In CI environments using --frozen-lockfile, installations will fail due to the mismatch. Without that flag, yarn may still install the old vulnerable version from the stale lockfile.

Fix in Cursor Fix in Web

},
"name": "next-plugins"
}