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

chore(deps): update npm to v8 [security] #27

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 24, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm (source) 7.24.2 -> 8.11.0 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2022-29244

Impact

npm pack ignores root-level .gitignore & .npmignore file exclusion directives when run in a workspace or with a workspace flag (ie. --workspaces, --workspace=<name>). Anyone who has run npm pack or npm publish with workspaces, as of v7.9.0 & v7.13.0 respectively, may be affected and have published files into the npm registry they did not intend to include.

Patch

  • Upgrade to the latest, patched version of npm (v8.11.0 or greater), run: npm i -g npm@latest
  • Node.js versions v16.15.1, v17.19.1 & v18.3.0 include the patched v8.11.0 version of npm

Steps to take to see if you're impacted

  1. Run npm publish --dry-run or npm pack with an npm version >=7.9.0 & <8.11.0 inside the project's root directory using a workspace flag like: --workspaces or --workspace=<name> (ex. npm pack --workspace=foo)
  2. Check the output in your terminal which will list the package contents (note: tar -tvf <package-on-disk> also works)
  3. If you find that there are files included you did not expect, you should:
    3.1. Create & publish a new release excluding those files (ref. "Keeping files out of your Package")
    3.2. Deprecate the old package (ex. npm deprecate <pkg>[@&#8203;<version>] <message>)
    3.3. Revoke or rotate any sensitive information (ex. passwords, tokens, secrets etc.) which might have been exposed

References


Release Notes

npm/cli (npm)

v8.11.0

Compare Source

v8.11.0 (2022-05-25)
Features
Bug Fixes
Documentation
Dependencies

v8.10.0

Compare Source

v8.10.0 (2022-05-11)
Features
Bug Fixes
Dependencies

v8.9.0

Compare Source

v8.9.0 (2022-05-04)
Features
Bug Fixes
Documentation
Dependencies

v8.8.0

Compare Source

v8.8.0 (2022-04-27)
Features
Bug Fixes
Documentation
Dependencies

v8.7.0

Compare Source

v8.7.0 (2022-04-13)
Features
Bug Fixes
Documentation
Dependencies

v8.6.0

Compare Source

v8.6.0 (2022-03-31)
Features
Bug Fixes
Documentation
Dependencies

v8.5.5

Compare Source

v8.5.5 (2022-03-17)

Bug Fixes
Documentation
Dependencies

v8.5.4

Compare Source

v8.5.4 (2022-03-10)

Bug Fixes
Documentation
Dependencies

v8.5.3

Compare Source

v8.5.3 (2022-03-03)

Bug Fixes
Dependencies

v8.5.2

Compare Source

v8.5.2 (2022-02-24)

Bug Fixes
Documentation
Dependencies

v8.5.1

Compare Source

v8.5.1 (2022-02-17)

Dependencies
Documentation

v8.5.0

Compare Source

v8.5.0 (2022-02-10)

Features

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot assigned C0ZEN Mar 24, 2023
@renovate renovate bot requested a review from C0ZEN March 24, 2023 13:52
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant