Skip to content

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

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 #14

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"
Copy link

@cursor cursor bot Dec 30, 2025

Choose a reason for hiding this comment

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

Major version upgrade breaks existing release scripts

Upgrading lerna from 3.x to 6.x introduces breaking changes that will cause the release-canary script to fail. The script uses --cd-version=prerelease and --npm-tag=canary options which were deprecated in lerna 4.x. In lerna 6.x, --cd-version is replaced with a positional bump argument (e.g., lerna publish prerelease) and --npm-tag was renamed to --dist-tag. The release workflow will break when someone attempts to publish canary releases.

Fix in Cursor Fix in Web

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