Update tar package version for tfjs-node & tfjs-node-gpu#8280
Merged
mattsoulanille merged 1 commit intomasterfrom May 21, 2024
Merged
Update tar package version for tfjs-node & tfjs-node-gpu#8280mattsoulanille merged 1 commit intomasterfrom
mattsoulanille merged 1 commit intomasterfrom
Conversation
pyu10055
approved these changes
May 20, 2024
mattsoulanille
approved these changes
May 21, 2024
This was referenced Jun 26, 2024
This was referenced Sep 9, 2024
This was referenced Sep 17, 2024
This was referenced Sep 30, 2024
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi, Team
We've identified that the @tensorflow/tfjs-node package currently specifies a dependency on
"tar": "^4.4.6". To address a known security vulnerability detailed in this GitHub security advisory: GHSA-f5x3-32g6-xq36, I've updated the tar dependency to a version"tar": "^6.2.1"to take care of this issue and I believe we'll have to release a patched version to npm. Thank you.