Skip to content

[13.x] Fix Illuminate\Http\Response compatibility against Symfony 8.1#60318

Merged
taylorotwell merged 2 commits into
13.xfrom
13/symfony-80100
May 29, 2026
Merged

[13.x] Fix Illuminate\Http\Response compatibility against Symfony 8.1#60318
taylorotwell merged 2 commits into
13.xfrom
13/symfony-80100

Conversation

@crynobone
Copy link
Copy Markdown
Member

@crynobone crynobone commented May 29, 2026

This avoids Symfony\Component\HttpFoundation\Response from throwing a deprecation when we set $headers property value in the constructor.

Alternative to #60303 and avoid making public API changes in a patch release. We can consider making the property type change for Laravel 14.

@crynobone crynobone force-pushed the 13/symfony-80100 branch 3 times, most recently from 19fc790 to 6acab91 Compare May 29, 2026 11:46
@crynobone crynobone marked this pull request as ready for review May 29, 2026 11:51
Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
@jnoordsij
Copy link
Copy Markdown
Contributor

It it just the int part of #60303 you're worried about? If so LMK and I'll ditch it. From the tests here and my experience you really need the additional changes from #60303 to get things working again.

@crynobone
Copy link
Copy Markdown
Member Author

There's multiple changes that is outside the scope of the main issue, which this PR only focuses on avoiding deprecation.

Signed-off-by: Mior Muhammad Zaki <crynobone@gmail.com>
Copy link
Copy Markdown
Collaborator

@GrahamCampbell GrahamCampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a much better approach.

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.

4 participants