Update GHSA-c59h-r6p8-q9wc.json#2902
Merged
advisory-database[bot] merged 1 commit intogithub:medikoo/advisory-improvement-2902from Oct 31, 2023
Merged
Update GHSA-c59h-r6p8-q9wc.json#2902advisory-database[bot] merged 1 commit intogithub:medikoo/advisory-improvement-2902from
advisory-database[bot] merged 1 commit intogithub:medikoo/advisory-improvement-2902from
Conversation
Do not affect `next` versions of previous `next` project
Contributor
|
Ah, I see |
4edfd46
into
github:medikoo/advisory-improvement-2902
Contributor
|
Hi @medikoo! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
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
2 participants
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.
Fix issue where security vulnerability is incorrectly applied to the v0.4 version of
nextwhich is a totally different product than one started at v0.9.9.Issue is that security is reported for packages that still depend on
next@0.4, which doesn't make sense. It was already discussed here, see #179 for contextNote: I wasn't able to introduce this change via suggest form as it exposes just "Affected versions" field, which logically would have to be
>=0.9.9 <13.4.20-canary.13and that's not accepted