Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

php-http/message-factory is abandoned (deprecation error) #85

Closed
tacman opened this issue May 30, 2023 · 5 comments · Fixed by #87
Closed

php-http/message-factory is abandoned (deprecation error) #85

tacman opened this issue May 30, 2023 · 5 comments · Fixed by #87

Comments

@tacman
Copy link
Contributor

tacman commented May 30, 2023

PHP version: x.y.z (hint: php --version)

all

Description

Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.

How to reproduce

composer install with any pacakge that uses it.

Possible Solution

use psr/http-factory instead

tacman added a commit to tacman/cache-plugin that referenced this issue May 30, 2023
use the recommended package, fixes php-http#85
@dbu
Copy link
Contributor

dbu commented Nov 15, 2023

fixed in #87

@dbu dbu closed this as completed Nov 15, 2023
@GrahamCampbell
Copy link
Contributor

Probably this should be kept open until v2.0.0 is released?

@jurgenhaas
Copy link

Is there anything that could be done to publish this soon, maybe even in the 1.x branch?

I'm asking because composer audit complains about the abandoned package and with composer 2.7 this even let's pipeline fail by default.

@dbu
Copy link
Contributor

dbu commented Feb 19, 2024

i tagged the 2.0 release now: https://github.com/php-http/cache-plugin/releases/tag/2.0.0

we still support antique php versions, therefore i did not add strict typing. but lets do that in a version 3 if somebody wants to put in the effort, rather than delay this release.

@dbu dbu closed this as completed Feb 19, 2024
@jurgenhaas
Copy link

Nice, thank you. Now we only have to get all the other packages that depend on the 1.0 release to update their constraints to also allow 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants