Wiz: Upgrade multiple dependencies (resolves 6 findings) - #1635
wiz-code-21c5ec5a85[bot] wants to merge 1 commit into
Conversation
|
🔗 Preview Mode
|
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5dae2a48da
ℹ️ 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.2", | ||
| "json-schema-merge-allof": "^0.8.1", | ||
| "lodash-es": "^4.17.21", | ||
| "lodash-es": "4.18.0", |
There was a problem hiding this comment.
Regenerate the lockfile with the dependency upgrades
In GitHub Actions, .github/actions/setup-pnpm/action.yml:35 runs a bare pnpm install; pnpm 10 documents in its error output that frozen-lockfile is true by default in CI. Because pnpm-lock.yaml still specifies js-yaml: ^4.1.1 and lodash-es: ^4.17.21, this change reproduces ERR_PNPM_OUTDATED_LOCKFILE, so every workflow using the shared setup action fails before tests, indexing, or deployment can run. Update and commit pnpm-lock.yaml alongside these manifest changes.
Useful? React with 👍 / 👎.
Wiz has created this PR to fix 6 findings detected in this project
Changes were made to the following file(s):
package.jsonVulnerabilities:
4.1.1 → 4.3.2
/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.