Skip to content
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

build(deps): bump tough-cookie and lerna #2371

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 8, 2023

Removes tough-cookie. It's no longer used after updating ancestor dependency lerna. These dependencies need to be updated together.

Removes tough-cookie

Updates lerna from 4.0.0 to 7.1.1

Release notes

Sourced from lerna's releases.

7.1.1

7.1.1 (2023-06-28)

Bug Fixes

  • fix strict-ssl mapping for node-fetch-registry during unpublished projects lookup (#3747) (5fcf94e)
  • publish: catch publish conflict 403 error from npm (#3753) (6123e86)
  • publish: ensure that error code is valid (#3748) (c59b45b)
  • schema: add missing ref to changelogEntryAdditionalMarkdown (b41afab)

7.1.0

7.1.0 (2023-06-25)

Features

  • core: export detectProjects utility function (#3740) (641fecb)
  • repair: add migration to remove unused "lerna" field from lerna.json (#3734) (4fb0427)
  • version: add --changelog-entry-additional-markdown option (#3751) (63671df)

7.0.2

7.0.2 (2023-06-15)

Bug Fixes

  • publish: revert auto-copying of assets to custom contents/directory (#3732) (70d4438)

7.0.1

7.0.1 (2023-06-13)

Bug Fixes

  • core: reset nx daemon after command finishes (#3726) (c0de66a)

7.0.0

7.0.0 (2023-06-08)

BREAKING CHANGES

After updating we strongly recommend running lerna repair in your project. This will migrate your lerna.json to the latest and greatest and remove any outdated options.

As this is a major release there are a few breaking changes to be aware of, which may or may not affect your lerna repos, depending on how you are using the tool.

  • legacy package management commands have been removed

We no longer include the bootstrap, add, and link commands by default. We strongly recommend using your package manager (npm, yarn, pnpm) for package management related concerns such as installing and linking dependencies.

... (truncated)

Changelog

Sourced from lerna's changelog.

7.1.1 (2023-06-28)

Bug Fixes

  • schema: add missing ref to changelogEntryAdditionalMarkdown (b41afab)

7.1.0 (2023-06-25)

Features

  • core: export detectProjects utility function (#3740) (641fecb)
  • repair: add migration to remove unused "lerna" field from lerna.json (#3734) (4fb0427)
  • version: add --changelog-entry-additional-markdown option (#3751) (63671df)

7.0.2 (2023-06-15)

Note: Version bump only for package lerna

7.0.1 (2023-06-13)

Note: Version bump only for package lerna

7.0.0 (2023-06-08)

Bug Fixes

Features

  • add migration for adding $schema, increase some strictness (73ceac3)

7.0.0-alpha.8 (2023-06-07)

Bug Fixes

Features

  • add migration for adding $schema, increase some strictness (73ceac3)

... (truncated)

Commits
  • 04642ff chore(misc): publish 7.1.1
  • b41afab fix(schema): add missing ref to changelogEntryAdditionalMarkdown
  • 2a6bb29 chore(misc): publish 7.1.0
  • 63671df feat(version): add --changelog-entry-additional-markdown option (#3751)
  • 641fecb feat(core): export detectProjects utility function (#3740)
  • 4fb0427 feat(repair): add migration to remove unused "lerna" field from lerna.json (#...
  • e6c7427 chore(misc): publish 7.0.2
  • 273ed54 chore(misc): publish 7.0.1
  • c81422d chore: add v7 release notes
  • 3900fe9 chore(misc): publish 7.0.0
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by jameshenry, a new releaser for lerna since your current version.


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Removes [tough-cookie](https://github.com/salesforce/tough-cookie). It's no longer used after updating ancestor dependency [lerna](https://github.com/lerna/lerna/tree/HEAD/packages/lerna). These dependencies need to be updated together.


Removes `tough-cookie`

Updates `lerna` from 4.0.0 to 7.1.1
- [Release notes](https://github.com/lerna/lerna/releases)
- [Changelog](https://github.com/lerna/lerna/blob/main/packages/lerna/CHANGELOG.md)
- [Commits](https://github.com/lerna/lerna/commits/7.1.1/packages/lerna)

---
updated-dependencies:
- dependency-name: tough-cookie
  dependency-type: indirect
- dependency-name: lerna
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 8, 2023
@socket-security
Copy link

Removed dependencies detected. Learn more about Socket for GitHub ↗︎

🚮 Removed packages: lerna@4.0.0

@socket-security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Native code @parcel/watcher 2.0.4
Install scripts nx 16.5.0
  • Install script: postinstall
  • Source: node ./bin/post-install

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore nx@16.5.0
  • @SocketSecurity ignore @parcel/watcher@2.0.4

@ckniffen
Copy link
Collaborator

@dependabot ignore this major version

This is superseded by #2342

@ckniffen ckniffen closed this Jul 10, 2023
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 10, 2023

This option is only available on single-dependency pull requests, as the versions in multi-dependency pull requests may differ.

If you'd like to ignore all updates for these dependencies just reply @dependabot ignore these dependencies.

@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 10, 2023

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/npm_and_yarn/tough-cookie-and-lerna--removed branch July 10, 2023 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant