Skip to content

Conversation

@aswinayyolath
Copy link
Contributor

@aswinayyolath aswinayyolath commented Jun 23, 2025

Updated Node packages to fix CVEs

Resolves: #368

Status

READY

Updated Node packages to fix CVEs

Resolves: ibm-messaging#368

Signed-off-by: Aswin A <[email protected]>
@aswinayyolath
Copy link
Contributor Author

Tested UI after the changes

Screenshot 2025-06-23 at 2 44 32 PM

Copy link

@oliver-wymer oliver-wymer left a comment

Choose a reason for hiding this comment

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

Approved but confused to see no updates to package.json itself.

@dalelane
Copy link

Approved but confused to see no updates to package.json itself.

I assume it's because only transitive dependencies are being updated

@aswinayyolath
Copy link
Contributor Author

I ran npm audit fix which updated the vulnerable transitive dependencies in package-lock.json but didn't require direct changes to package.json. since top level dep themselves remained the same.

Updated GitHub Actions to latest stable versions.

Resolves: ibm-messaging#368

Signed-off-by: Aswin A <[email protected]>
Athira Sreekumar and others added 2 commits July 22, 2025 14:31
fixes lint errors

Contributes to: ibm-messaging#368

Signed-off-by: Athira Sreekumar <[email protected]>
updated node-pr.jobs to fix CI issues

Resolves: ibm-messaging#368

Signed-off-by: Aswin A <[email protected]>
@aswinayyolath
Copy link
Contributor Author

Closing as there is another PR which resolves this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix CVE in @babel/traverse via upgrade to safe versions

4 participants