Requesting a quick patch to 6.5.8 to fix fatal error if guzzle 6.x and 7.x exist concurrently about guzzle

[GrahamCampbell]

Thanks for getting in touch. Guzzle 6 has been out of bug-fix support for some time, and completely EOL since the end of October 2023, which is more than 6 months ago. For this reason, we won't be making such a change. The maintainer of the package can either edit the code they are bundling or upgrade to Guzzle 7. We intentionally made the upgrading path as easy as possible.

[figureone]

100% sympathize with your decision. Just want you to be aware that the decision does harm folks using Guzzle 7 (because there are other folks out there that refuse to upgrade for whatever reason). Only reason I opened the issue is because it's a one-line change that's already been tested and deployed in w3-total-cache (over 1 million active installs), so I thought the burden on you as maintainers was minimal. But I can understand it might open the flood gates for other backported fixes.

Carry on, thanks for maintaining an awesome library!