Skip to content

Add support for Symfony 8#436

Merged
TravisCarden merged 3 commits intophp-tuf:developfrom
longwave:symfony-8
Feb 4, 2026
Merged

Add support for Symfony 8#436
TravisCarden merged 3 commits intophp-tuf:developfrom
longwave:symfony-8

Conversation

@longwave
Copy link
Contributor

@longwave longwave commented Jan 28, 2026

Drupal depends on php-tuf/composer-stager, and Drupal 12 will require Symfony 8, so in turn this package needs to support it.

Locally I get the same test failures on develop (on PHP 8.3 or 8.4) and this branch (on PHP 8.4):

ERRORS!
Tests: 524, Assertions: 1661, Errors: 17, Failures: 24, Warnings: 7.

@TravisCarden
Copy link
Collaborator

Thanks, @longwave. I'll look into this as soon as I can carve out some time.

@TravisCarden
Copy link
Collaborator

That should do it, @longwave! Before I merge, should we cut a new major branch and simultaneously add Symfony 8.x support and drop earlier versions? Should we create a new issue to discuss with other stakeholders?

@longwave
Copy link
Contributor Author

longwave commented Feb 4, 2026

Do we need a new major here? I think adding support for a new Symfony is fine in a minor version; you aren't removing any API.

As a parallel asm89/stack-cors is also a core dependency, they added Symfony 8 support in a new minor: https://github.com/asm89/stack-cors/releases/tag/v2.4.0

@TravisCarden
Copy link
Collaborator

I think adding support for a new Symfony is fine in a minor version; you aren't removing any API.

I'm fine with that, as long as everyone who needs to approve the decision approves it. (I don't know who that would be, but I assumed it would require more than two people.)

I'm also wondering about removing support for Symfony 6 & 7, which obviously would need to be a major version change. And if we chose to do that, I wondered if we should do both things at once. I originally just used whatever versions Drupal core used. I haven't yet had to ask what happens when that changes.

@catch56
Copy link

catch56 commented Feb 4, 2026

I think if it's easy to add support for Symfony 8 that's good to do in a minor. And then dropping Symfony 6/7 support could happen in a new major.

The advantage of this is that it allows sites to update to a version of composer stager that allows Symfony 8, then update to Symfony 8, then update to the major version of composer stager in three different steps if they want/need to for any reason.

@longwave
Copy link
Contributor Author

longwave commented Feb 4, 2026

Also, do we need to drop support for older Symfony? As we have passing tests and we haven't need to make any code changes to support the latest Symfony, we might as well keep as wide a range of compatibility as we can.

@TravisCarden
Copy link
Collaborator

Cool. Well, I'm going to consider three people a consensus 😄 and merge and release this in a minor right now. We can discuss dropping old Symfony versions at a later date.

@TravisCarden TravisCarden added enhancement New feature or request dependencies Pull requests that update a dependency file labels Feb 4, 2026
@TravisCarden TravisCarden changed the title Allow Symfony 8, bump lockfile versions. Add support for Symfony 8 Feb 4, 2026
@TravisCarden TravisCarden merged commit cb62f27 into php-tuf:develop Feb 4, 2026
14 checks passed
@TravisCarden
Copy link
Collaborator

TravisCarden commented Feb 4, 2026

It's all yours! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants