[Security] update @unvt/sprite-one v0.0.9 to v0.1.1 #174
+716
−629
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.
TL;DR
@unvt/sprite-one
to v0.1.1.@unvt/sprite-one
depends onsharp
, which only officially supports Node.js v18 and above@unvt/charites
will continue to support Node.js v14, v16.github/workflows/build.yml
Description
@unvt/charites
includes@unvt/sprite-one
in dependencies.@unvt/sprite-one
v0.0.9 includessharp
in dependencies.sharp
includeslibwebp
in dependencies.libwebp
is vulnerable to CVE-2023-4863.Fortunately, this vulnerability has already been fixed.
@unvt/sprite-one
to v0.1.1.So,
@unvt/sprite-one
to v0.1.1.Type of Pull Request
Verify the followings
main
branchnpm run build
npm run lint
charites help
globallyRefer to CONTRIBUTING.MD for more details.