Skip to content
This repository was archived by the owner on Feb 28, 2023. It is now read-only.

chore(deps): update dependency npm to 8.11.0 [security] #232

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 2, 2022

Mend Renovate

This PR contains the following updates:

Package Change
npm 7.24.2 -> 8.11.0

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


Configuration

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

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 7 times, most recently from 9a00a99 to b1e61a7 Compare June 12, 2022 13:12
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 5 times, most recently from 5ca7585 to 56933f5 Compare June 17, 2022 02:06
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 6 times, most recently from 554a059 to 7881259 Compare June 25, 2022 14:47
@renovate renovate bot changed the title chore(deps): update dependency npm to 8.11.0 [security] chore(deps): update dependency npm to 8.11.0 [SECURITY] Jun 27, 2022
@renovate renovate bot changed the title chore(deps): update dependency npm to 8.11.0 [SECURITY] chore(deps): update dependency npm to 8.11.0 [security] Jun 28, 2022
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 8 times, most recently from e8035ae to f867234 Compare July 4, 2022 21:42
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 3 times, most recently from b9925f2 to 8bda4c1 Compare October 12, 2022 18:51
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 2 times, most recently from f650ff0 to 658af51 Compare October 21, 2022 12:16
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 2 times, most recently from d85a105 to 6ea16b2 Compare October 25, 2022 21:24
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 2 times, most recently from 4088cc4 to 87a4da1 Compare November 15, 2022 22:07
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from 87a4da1 to e49404b Compare November 26, 2022 07:48
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from e49404b to dcf7fe4 Compare December 8, 2022 15:57
@renovate renovate bot changed the title chore(deps): update dependency npm to 8.11.0 [security] chore(deps): update dependency npm to 8.11.0 [security] - autoclosed Dec 9, 2022
@renovate renovate bot closed this Dec 9, 2022
@renovate renovate bot deleted the renovate/npm-npm-vulnerability branch December 9, 2022 16:38
@renovate renovate bot changed the title chore(deps): update dependency npm to 8.11.0 [security] - autoclosed chore(deps): update dependency npm to 8.11.0 [security] Dec 13, 2022
@renovate renovate bot reopened this Dec 13, 2022
@renovate renovate bot restored the renovate/npm-npm-vulnerability branch December 13, 2022 16:24
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from dcf7fe4 to db0b9fe Compare December 13, 2022 19:48
@renovate renovate bot changed the title chore(deps): update dependency npm to 8.11.0 [security] Update dependency npm to 8.11.0 [SECURITY] Dec 17, 2022
@renovate renovate bot changed the title Update dependency npm to 8.11.0 [SECURITY] chore(deps): update dependency npm to 8.11.0 [security] Dec 17, 2022
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch 4 times, most recently from 6212f85 to 50ec259 Compare December 28, 2022 20:19
@renovate renovate bot force-pushed the renovate/npm-npm-vulnerability branch from 50ec259 to ff7b79e Compare January 3, 2023 23:37
@emilyrohrbough
Copy link
Member

closed in favor of #234

@renovate
Copy link
Contributor Author

renovate bot commented Jan 3, 2023

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (8.11.0). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.

@renovate renovate bot deleted the renovate/npm-npm-vulnerability branch January 3, 2023 23:42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant