fix(ghsa): add support of last_known_affected_version_range field
#392
Conversation
This file contains 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
DmitriyLewen
force-pushed
the
fix-ghsa/last-known-affected
branch
from
df48c8f to
58951d4
Compare
Signed-off-by: knqyf263 <[email protected]>
knqyf263
force-pushed
the
fix-ghsa/last-known-affected
branch
from
8258c59 to
720537e
Compare
knqyf263
approved these changes
Apr 1, 2024
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.
Description
There two cases when
GHSAuseslast_known_affected_version_rangefield - github/advisory-database#470 (comment).We need to add version for case when
last_known_affected_version_range fieldis exist andfixed/last_affectedfield doesn't exist.Related Issues
last_known_affected_version_range#391