-
Notifications
You must be signed in to change notification settings - Fork 4k
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.
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
chore(deps): Upgrade major version of lerna #13723
Conversation
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAIK, we don't use any of the features that are breaking in lerna-4.x
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
With the exception of dropping support for Node 6.x & 8.x, all other breaking changes were "internal" packages. |
This resolves https://github.com/aws/aws-cdk/security/dependabot/yarn.lock/ssri/open Lerna is the root of the dependency chain causing this security alert. ```console => Found "ssri@6.0.1" info Reasons this module exists - "_project_#lerna#@lerna#publish#@evocateur#pacote" depends on it - Hoisted from "_project_#lerna#@lerna#publish#@evocateur#pacote#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@evocateur#npm-registry-fetch#make-fetch-happen#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@evocateur#pacote#cacache#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@lerna#pack-directory#@lerna#get-packed#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@lerna#npm-publish#@evocateur#libnpmpublish#ssri" ``` Unfortunately upgrading all transitive deps of the latest lerna version for `3.x` doesn't pull the necessary upgrade to resolve the alert. So it's either: 1. Wait for lerna to release a `3.x` patch to resolve this, which doesn't seem likely since the alert refers to a deep transitive dependency. 2. Manually and selectively upgrade the `ssri` package to a new major version - feels fragile. 3. Upgrade to lerna `4.x`. Opted for option 3 since it sounds the most reasonable. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This resolves https://github.com/aws/aws-cdk/security/dependabot/yarn.lock/ssri/open Lerna is the root of the dependency chain causing this security alert. ```console => Found "ssri@6.0.1" info Reasons this module exists - "_project_#lerna#@lerna#publish#@evocateur#pacote" depends on it - Hoisted from "_project_#lerna#@lerna#publish#@evocateur#pacote#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@evocateur#npm-registry-fetch#make-fetch-happen#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@evocateur#pacote#cacache#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@lerna#pack-directory#@lerna#get-packed#ssri" - Hoisted from "_project_#lerna#@lerna#publish#@lerna#npm-publish#@evocateur#libnpmpublish#ssri" ``` Unfortunately upgrading all transitive deps of the latest lerna version for `3.x` doesn't pull the necessary upgrade to resolve the alert. So it's either: 1. Wait for lerna to release a `3.x` patch to resolve this, which doesn't seem likely since the alert refers to a deep transitive dependency. 2. Manually and selectively upgrade the `ssri` package to a new major version - feels fragile. 3. Upgrade to lerna `4.x`. Opted for option 3 since it sounds the most reasonable. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This resolves https://github.com/aws/aws-cdk/security/dependabot/yarn.lock/ssri/open
Lerna is the root of the dependency chain causing this security alert.
Unfortunately upgrading all transitive deps of the latest lerna version for
3.x
doesn't pull the necessary upgrade to resolve the alert.So it's either:
3.x
patch to resolve this, which doesn't seem likely since the alert refers to a deep transitive dependency.ssri
package to a new major version - feels fragile.4.x
.Opted for option 3 since it sounds the most reasonable.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license