Problem
Version 5.0.0 and the current master branch constrain Guzzle to version 7:
"guzzlehttp/guzzle": "^7.8"
This blocks downstream applications from adopting Guzzle 8 while continuing to use the SCORM Cloud PHP client.
A minimal conflict can be reproduced with:
composer require rustici-software/scormcloud-api-v2-client-php:^5 guzzlehttp/guzzle:^8.0
Composer rejects the graph because the client currently permits Guzzle 7 only.
Request
Could Guzzle 8 compatibility be evaluated and supported in a release?
Ideally this would include:
- testing generated API-client behavior against Guzzle 8;
- making or regenerating any source changes required by its breaking changes;
- adding Guzzle 8 to the CI dependency matrix; and
- widening the Composer constraint once compatibility is verified.
Related: #17 tracked the equivalent constraint update from Guzzle 6 to Guzzle 7.
Problem
Version 5.0.0 and the current master branch constrain Guzzle to version 7:
This blocks downstream applications from adopting Guzzle 8 while continuing to use the SCORM Cloud PHP client.
A minimal conflict can be reproduced with:
Composer rejects the graph because the client currently permits Guzzle 7 only.
Request
Could Guzzle 8 compatibility be evaluated and supported in a release?
Ideally this would include:
Related: #17 tracked the equivalent constraint update from Guzzle 6 to Guzzle 7.