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] #108

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 3, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
npm (source) ^7.0.8 -> ^8.0.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
Dependencie

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

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

Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from 7a7e7d7 to 3639f76 Compare April 3, 2023 22:33
@renovate renovate bot changed the title chore(deps): update npm to v8 [security] chore(deps): update dependency npm to 8.11.0 [security] Apr 3, 2023
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 2 times, most recently from 0f05bf7 to c2f3f24 Compare April 18, 2023 10:19
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from c2f3f24 to cd63208 Compare May 28, 2023 10:07
@renovate renovate bot changed the title chore(deps): update dependency npm to 8.11.0 [security] chore(deps): update npm to v8 [security] May 28, 2023
@renovate renovate bot changed the title chore(deps): update npm to v8 [security] chore(deps): update npm to v8 [security] - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/npm-npm-vulnerability branch December 8, 2024 18:48
@renovate renovate bot changed the title chore(deps): update npm to v8 [security] - autoclosed chore(deps): update npm to v8 [security] Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from 816f15f to cd63208 Compare December 8, 2024 23:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants