Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"dependencies": {
"byots": "3.9.0-dev.20200325.13.13",
"fs-extra": "^7.0.1",
"lodash": "^4.17.14",
"lodash": "^4.17.23",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate lockfile so installs use patched lodash

If CI or users run npm ci (or otherwise rely on the committed lockfile), they will still get the older lodash versions that remain in package-lock.json (e.g., 4.17.19/4.17.13), so the vulnerability fix from this bump won’t actually be applied. Please update and commit package-lock.json alongside this change to ensure the patched version is installed.

Useful? React with 👍 / 👎.

"semver": "^6.2.0",
"ts-diagnostic-formatter": "^0.1.1",
"yargs": "^13.2.4"
Expand Down Expand Up @@ -80,7 +80,7 @@
"@semantic-release/changelog": "^3.0.2",
"@semantic-release/commit-analyzer": "^6.1.0",
"@semantic-release/git": "^7.0.8",
"@semantic-release/npm": "^5.1.8",
"@semantic-release/npm": "^7.1.0",
"@semantic-release/release-notes-generator": "^7.1.4",
"@types/fs-extra": "^5.1.0",
"@types/lodash": "^4.14.132",
Expand All @@ -94,7 +94,7 @@
"conventional-changelog": "^3.1.3",
"conventional-changelog-cli": "^2.1.0",
"esbuild": "^0.8.39",
"eslint": "^6.6.0",
"eslint": "^9.0.0",
"eslint-plugin-import": "^2.18.2",
"eslint-plugin-jsdoc": "^17.1.1",
"eslint-plugin-no-null": "^1.0.2",
Expand Down