chore: bump oauth2-apple to allow php-jwt 7.x#2135
Merged
Conversation
Member
|
Perfect, can you rebase on 3.x though? |
Contributor
Author
I'll check that I've probably created my branch from another one by mistake |
MrYamous
force-pushed
the
update-dependency-for-phpjwt
branch
from
8ae8620 to
bb200ab
Compare
MrYamous
changed the title
oauth2-apple to allow php-jwt 7.xoauth2-apple to allow php-jwt 7.x
Contributor
Author
Done @brendt |
Member
|
Thanks :) |
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.
I suggests to update
patrickbussmann/oauth2-appledependency to 0.4Why ?
While running a composer update, Composer reported a security vulnerability advisory about
firebase/php-jwtpackageSee Github advisory
A composer why later, I found this package was stick to
firebase/php-jwt 6.0but 0.4 solves this without introducing BC