Repository navigation
Wiz: Upgrade multiple dependencies (resolves 6 findings) - #1697
wiz-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: 451e66bf7a
ℹ️ 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.
The committed pnpm-lock.yaml still specifies js-yaml as ^4.1.1/4.1.1 and lodash-es as ^4.17.21/4.17.23, so it is out of sync with these manifest changes. Every checked workflow installs through .github/actions/setup-pnpm/action.yml:35, and pnpm documents that CI enables frozen-lockfile behavior and fails when the lockfile and manifest differ; reproducing that install reports ERR_PNPM_OUTDATED_LOCKFILE for both dependencies. Commit the regenerated pnpm-lock.yaml so PR checks and deployment/indexing workflows can install dependencies and the security upgrades are actually locked.
Useful? React with 👍 / 👎.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.