Fix critical and high dependency alerts#52
Open
lancewillett wants to merge 1 commit into
Open
Conversation
474cbcf to
a396eb7
Compare
a396eb7 to
8a042cd
Compare
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
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.
Summary
firebase/php-jwtto a PHP 7.3-compatible 6.x release to clear the critical JWT advisory without changing the repo's advertised PHP 7.3 runtime floor.illuminate/database,phpunit/phpunit,nesbot/carbon, PHPCS tooling, and Psalm, so current Composer can install the lockfile.uuiddependency and generate the test APNS ID with Node's built-incryptomodule instead.Validation
Notes
composer audit --lockedstill reports the low-severityfirebase/php-jwtadvisory fixed in 7.x. Moving tophp-jwt7.x requires PHP 8.0+, so this PR keeps the PHP 7.3 contract and clears the critical/high/medium Composer advisories.Build and Testjob currently runs the full PHPUnit suite successfully and generates coverage, then fails while uploading coverage through the legacy CodeClimate reporter path. The old CodeClimate binary URL now returns 404, so this PR uses the archived reporter release with a pinned checksum; the upload still exits non-zero and likely needs an owner decision on the stale CodeClimate required checks.