Skip to content

Prepare release v0.12.4 #456

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

Merged
merged 5 commits into from
Jan 20, 2022
Merged

Prepare release v0.12.4 #456

merged 5 commits into from
Jan 20, 2022

Conversation

bocharsky-bw
Copy link
Member

Closes #454

@rvanlaak
Copy link
Member

Seems Psr\Http\Client\ClientInterface::sendRequest(Psr\Http\Message\RequestInterface $request) added the Psr\Http\Message\ResponseInterface typehint on the return value. Should that not be considered a BC break from PSR-perspective? Would it require us to pin the PSR package?

@welcoMattic
Copy link
Member

Seems Psr\Http\Client\ClientInterface::sendRequest(Psr\Http\Message\RequestInterface $request) added the Psr\Http\Message\ResponseInterface typehint on the return value. Should that not be considered a BC break from PSR-perspective? Would it require us to pin the PSR package?

As we plan to make a stable release in the coming months, I guess we can pin the PSR package, and update the typehint on the return type in 1.0?

@bocharsky-bw
Copy link
Member Author

Hm, in which PR that change you're talking about was done that will cause BC breaks? I don't see this change in the PRs I listed in this release somehow.

@gimler
Copy link
Contributor

gimler commented Jan 6, 2022

any news? @welcoMattic @bocharsky-bw

@tchapi
Copy link

tchapi commented Jan 6, 2022

Hello !
Any update on this merge so we can have a new release ? Do you need any help ?

Thanks a lot !

@gimler
Copy link
Contributor

gimler commented Jan 19, 2022

@rvanlaak can you answer the question from @bocharsky-bw please

@tchapi
Copy link

tchapi commented Jan 19, 2022

I think the typehint was there since the beginning: See the initial commit for this interface here: php-fig/http-client@0950508#diff-7fe9d7bab1528c58fb39365621c6f02430dd01828c26fe8b00f0408de72c71b8

I don't really see a BC break here, but maybe I'm not lookng at the right thing

@rvanlaak
Copy link
Member

@gimler my comment was related to the failing tests. See the PHP 8.0 test run for example:

https://github.com/php-translation/symfony-bundle/runs/4299001816?check_suite_focus=true#step:6:10

@bocharsky-bw
Copy link
Member Author

If I understand correctly, the latest bundle's release (which is 0.12.3) also fails on that PHP 8.0 job you mentioned, right? If so, then the latest release has broken tests as well. With the new release, we will just bring some good changes to the users they are so waiting for, but some tests will still fail. I don't think broken tests is a blocker for making releases if those tests are also broken in the latest release, or am I wrong? Probably broken tests will be fixed completely in further releases, and we will make another release with all green tests. Does it make sense? If not, what steps exactly do you suggest to achieve a new release for today?

@bocharsky-bw bocharsky-bw mentioned this pull request Jan 19, 2022
@bocharsky-bw
Copy link
Member Author

All tests were fixed in #458 - please, give a review and share your thoughts

@bocharsky-bw
Copy link
Member Author

I think this one is ready now

@bocharsky-bw
Copy link
Member Author

Thank you for the review, guys!

@bocharsky-bw bocharsky-bw merged commit d9d71b1 into master Jan 20, 2022
@bocharsky-bw bocharsky-bw deleted the v0.12.4 branch January 20, 2022 09:27
@bocharsky-bw
Copy link
Member Author

Tag 0.12.4 was created 🎉

https://github.com/php-translation/symfony-bundle/tree/0.12.4

Thanks everyone for the patience!

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

Successfully merging this pull request may close these issues.

New release please
5 participants