Actual reason of Laravel and PHP version increase?

[serious-angel]

Dear Developer and Artists,

Thank you for the marvel you do!

Apparently, the versions of dependencies in the library version 3.5.0 got a relatively huge increase: 9e44e2c

In production/enterprise, I know at least 3 active projects that are literally too huge to upgrade both Laravel from 10 to 12, and PHP from 8.1 to 8.2 even, at this particular moment. These are finance related, with tens of thousands Users, and the developers are working on it as much as they can.

Not to mention that the library works flawlessly with the previous dependencies I do believe.

Sure, perhaps you got everything up-to-date and running, but have you considered the projects that depend on it in global viewpoint? It seems utterly adequate to allow at least a few years for projects to upgrade such low-level dependencies as the framework and PHP itself.

That said, @freekmurze , may I ask what is the actual reason of hard-increasing the dependency versions?

Best and kind regards

[ceejayoz]

https://www.php.net/supported-versions indicates 8.1 was EOLed in 2023 and stops receiving even security updates next month. No "finance related" tooling should be using an unsupported version of PHP.

[serious-angel]

https://www.php.net/supported-versions indicates 8.1 was EOLed in 2023 and stops receiving even security updates next month. No "finance related" tooling should be using an unsupported version of PHP.

You live in the "ideal" world, aren't you? With many colleagues, big teams, great salaries?
Or do you develop/maintain/operate tiny businesses only?
Congratulations.

Roger that. I'll suggest them maintain their own dev-* fork branch for Composer (i.e. alias) until they'll update their base environment.