Wiz: Upgrade multiple dependencies (resolves 5 findings) - #1517
Wiz: Upgrade multiple dependencies (resolves 5 findings)#1517wiz-code-21c5ec5a85[bot] wants to merge 1 commit into
Conversation
|
🔗 Preview Mode
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 518681ccf7
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "js-yaml": "4.3.1", | ||
| "json-schema-merge-allof": "^0.8.1", | ||
| "lodash-es": "^4.17.21", | ||
| "lodash-es": "4.18.0", |
There was a problem hiding this comment.
Because this commit changes package.json without updating pnpm-lock.yaml, the root importer still pins js-yaml to ^4.1.1/4.1.1 and lodash-es to ^4.17.21/4.17.23. In the GitHub workflows I checked, .github/actions/setup-pnpm/action.yml runs pnpm install; the pnpm install docs say CI defaults to frozen lockfile and fails when the lockfile is out of sync with the manifest. As a result, PR checks that use the shared setup action will fail before these upgrades are installed, and the intended vulnerability remediation will not actually take effect.
Useful? React with 👍 / 👎.
Wiz has created this PR to fix 5 findings detected in this project
Changes were made to the following file(s):
package.jsonVulnerabilities:
4.1.1 → 4.3.1
/package.json4.17.23 → 4.18.0
/package.jsonTo detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio.