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

Drop support for Symfony v4 #6108

Merged
merged 1 commit into from Jan 14, 2022
Merged

Drop support for Symfony v4 #6108

merged 1 commit into from Jan 14, 2022

Conversation

keradus
Copy link
Member

@keradus keradus commented Nov 15, 2021

No description provided.

@coveralls
Copy link

coveralls commented Nov 15, 2021

Coverage Status

Coverage remained the same at 93.149% when pulling 9c81d03 on keradus:sf4 into 01a0cf4 on FriendsOfPHP:master.

composer.json Outdated Show resolved Hide resolved
@SpacePossum
Copy link
Contributor

Do we have an idea how many users are "stuck" on SF4 that (still) use the tool as a direct (dev) dependency in their composer.json?

@keradus
Copy link
Member Author

keradus commented Nov 19, 2021

very good question, @SpacePossum .
I already run "experimental" releases (published together) to collect the numbers

3.3.0 - regular release
3.3.1 - PHP 7.2 required
3.3.2 - PHP 7.2 required + Symfony 5 required

so far...

3.3.0 -   65 installations
3.3.1 -  140 installations
3.3.2 - 2300 installations

@GrahamCampbell
Copy link
Contributor

I'm not sure dropping this adds much value. We don't have any 4.x specific work arounds in the codebase?

@keradus
Copy link
Member Author

keradus commented Dec 11, 2021

during the last call, we decided to not include it in newest release that is adding support for PHP 8.1.
I would like to include it in next release.

Copy link
Member

@localheinz localheinz left a comment

Choose a reason for hiding this comment

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

👍

SpacePossum added a commit that referenced this pull request Dec 22, 2021
This PR was squashed before being merged into the master branch (closes #6203).

Discussion
----------

Bump required PHP to 7.4

After merge of this PR, merge #6108 also!

-------

- ~5% of ppl (who are updating) would be affected: https://packagist.org/packages/friendsofphp/php-cs-fixer/php-stats#3.4
- best to review commit by commit
 -- update 70205
 -- update 7.2.5
 -- update Docker
 -- update CI

Commits
-------

c619e16 Bump required PHP to 7.4
@keradus keradus added the RTM Ready To Merge label Dec 23, 2021
@94noni
Copy link
Contributor

94noni commented Dec 23, 2021

Hi, Symfony v4.4 is an LTS and will be supported until EO 2022 (2023)
Will this be released for a csfixer v4? or v3.x? thank you

@GrahamCampbell
Copy link
Contributor

v3

@SpacePossum SpacePossum removed the RTM Ready To Merge label Dec 23, 2021
@keradus keradus added the RTM Ready To Merge label Jan 2, 2022
@keradus keradus removed the RTM Ready To Merge label Jan 14, 2022
@keradus keradus merged commit 626c3a8 into PHP-CS-Fixer:master Jan 14, 2022
@keradus keradus deleted the sf4 branch January 14, 2022 00:25
@SpacePossum
Copy link
Contributor

Will this be released for a csfixer v4? or v3.x? thank you

since it is merged now you can expect it in v3.6.0

@keradus
Copy link
Member Author

keradus commented Jan 14, 2022

actually released as v3.5.0

@GPHemsley-RELX
Copy link

This seems to me to be a strange decision given that Symfony 4.4 is LTS and there are no Symfony 4.x-specific workarounds in the codebase that would benefit from this - which are both points raised by others above.

I'm also not clear why this was so tightly coupled with the dropping of support for versions of PHP prior to 7.4. Symfony 4.4 supports PHP 7.4.

I am not "stuck" on Symfony 4.4. I have made the deliberate decision to take advantage of the LTS period and not update Symfony yet. But that doesn't mean I'm not updating PHP-CS-Fixer along the way.

@derrabus
Copy link
Contributor

derrabus commented Feb 3, 2022

This seems to me to be a strange decision given that Symfony 4.4 is LTS and there are no Symfony 4.x-specific workarounds in the codebase that would benefit from this - which are both points raised by others above.

Before this change, PHP CS Fixer supported a span of three Symfony major versions. That alone complicates the test matrix and makes developing new functionality tedious. It also prevented this project from taking advantage of Symfony 5 features until now. The reason behind Symfony's LTS period is to give everyone enough time to upgrade at their own pace. No downstream open-source project should feel obliged to support an LTS branch until the very last minute.

Given that this project is maintained by a handfull of developers in their freetime, I find this change very reasonable.

I am not "stuck" on Symfony 4.4. I have made the deliberate decision to take advantage of the LTS period and not update Symfony yet.

Well and this project has made the deliberate decision to abandon Symfony 4.4. A perfectly valid decision which should be respected. PHP CS Fixer supports the current Symfony LTS which is 5.4, see https://symfony.com/releases.

If you insist on staying on Symfony 4.4 (which is totally fine!), these are your options:

@keradus
Copy link
Member Author

keradus commented Feb 7, 2022

@GPHemsley-RELX , would you like to try shim package?

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.

None yet

9 participants