Match jwt-framework versions with FriendsOfPHP/security-advisories - #153
Closed
oldpec wants to merge 1 commit into
Closed
Match jwt-framework versions with FriendsOfPHP/security-advisories#153oldpec wants to merge 1 commit into
oldpec wants to merge 1 commit into
Conversation
Member
|
This library is re-generated hourly, so changing the range manually has no effect: it is possible to exclude a specific GH Advisory. See for example Roave/SecurityAdvisoriesBuilder#780 |
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.
Matching versions as per https://github.com/FriendsOfPHP/security-advisories/pull/789/changes#diff-4af58925f5064620bbf9bc5563ca9aceeef7c8f576c74ad08c230dee9ddfe8b7
I think:
GHSA-jc38-x7x8-2xc8
has the wrong versions on it and the problem has actually been fixed on branches
3.4.10 (link is for 3.4.11, but I think it is just adding tests and fix was on 3.4.10)
4.0.7
4.1.7
but automation has pulled in the version from the GHSA
See also issues :
web-token/jwt-framework#657
#152