Skip to content

fix(deps): update dependency npm to v8 [security]#307

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-npm-vulnerability
Closed

fix(deps): update dependency npm to v8 [security]#307
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-npm-vulnerability

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 20, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
npm (source) ^7.19.0^8.0.0 age 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

Configuration

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

🚦 Automerge: Enabled.

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from Jxio, ochiu and seeker25 as code owners February 20, 2026 15:53
@seeker25 seeker25 closed this Feb 20, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Feb 20, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/npm-npm-vulnerability branch February 20, 2026 15:57
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.

1 participant