Update dependencies to recent versions - #1560
Conversation
Signed-off-by: Alexander Wels <awels@redhat.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
|
||
| "@types/node-forge@npm:^1.3.0": | ||
| version: 1.3.11 | ||
| resolution: "@types/node-forge@npm:1.3.11" |
There was a problem hiding this comment.
here node-forge 1.3.1 is removed from yarn.lock, is this package no longer used, or should it be upgraded to >= 1.3.2 to fix CVE-2025-12816 and CVE-2025-66031 ?
there are 2 jira tickets related to this
There was a problem hiding this comment.
yes node-forge has been removed, if you look at the webpack-dev-server 5.x upgrade output, selfsigned the only package that depended on node-forge was removed. So it is no longer needed.
No description provided.