I've upgraded GuzzleHttp to the latest minor version and refactored the tests to remove deprecation warnings, caused by GuzzleHttp deprecating ClientInterface::getConfig (removing it in the upcoming major version - v8.0)
I've also locked firebase/php-jwt to v6.3.x using the tilde (~) selector rather than caret (^) this is, because installing packages using the previous behaviour would install minor versions up to 6.x.x, which would raise the required PHP version to 7.4 (see release notes of firebase/php-jwt@6.5.0)
It's noteworthy, that php-jwt@6.4.0 still supports PHP 7.2 just fine and will be the last minor release not requiring to raise the required PHP version for the client.
I've upgraded
GuzzleHttp
to the latest minor version and refactored the tests to remove deprecation warnings, caused by GuzzleHttp deprecatingClientInterface::getConfig
(removing it in the upcoming major version - v8.0)I've also locked
firebase/php-jwt
to v6.3.x using the tilde (~) selector rather than caret (^) this is, because installing packages using the previous behaviour would install minor versions up to 6.x.x, which would raise the required PHP version to 7.4 (see release notes of firebase/php-jwt@6.5.0)It's noteworthy, that php-jwt@6.4.0 still supports PHP 7.2 just fine and will be the last minor release not requiring to raise the required PHP version for the client.
fixes #104 closes #101