The old Flex infrastructure is shutting down

In September 2021, we announced that we were transitioning the Flex infrastructure to a public Github repository. In November 2021, we wrote a blog post explaining how to transition (short version: upgrade to the latest symfony/flex version). Since then, I've been monitoring the number of downloads for the old Flex package versions on Packagist and the traffic on the private infrastructure. It took a while to see fewer downloads on Packagist, but the traffic was still massive without a decrease. To help people using Flex via another project, we have made some pull requests like for Bolt. I have also posted some tweets to warn users like Sept 23, Dec 22, and March 9 for instance. Still, the traffic did not decrease. We have used many techniques to try forcing people to upgrade like adding a warning whenever you require a new dependency, making the server way slower by adding a 10-second sleep for each request to the server, and some more. Still, the traffic did not decrease. A few weeks ago, I decided to go one step further by intentionally returning empty data for any request to break the Composer workflow. And some people noticed. They upgraded. Still, the traffic did not decrease in any significant way. Today, I am confident that all "real projects" have been migrated. The traffic must come from bots or broken CIs. In any case, from projects for which nobody cares. That's why it's time to shut down the old infrastructure. For projects that did not upgrade yet, that does not change anything as the workflow is already broken anyway. And the fix is known and "easy".

                Sponsor the Symfony project.

https://symfony.com/blog/the-old-flex-infrastructure-is-shutting-down?utm_source=Symfony%20Blog%20Feed&utm_medium=feed

Creado 3y | 1 may 2022, 18:20:18


Inicia sesión para agregar comentarios

Otros mensajes en este grupo.

New in Symfony 7.3: DX Improvements (part 2)

This is the second part of the blog post showcasing the main DX (developer experience) features introduced in Symfony 7.3. Read the first part of this blog post.

Verify URI Signatures… https://symfon

29 may 2025, 9:10:19 | Symfony
Symfony 6.4.22 released

Symfony 6.4.22 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in you

29 may 2025, 9:10:19 | Symfony
Symfony 7.2.7 released

Symfony 7.2.7 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your

29 may 2025, 9:10:18 | Symfony
Symfony 7.3.0 released

Symfony 7.3.0 has just been released. Check the New in Symfony 7.3 posts on this blog to learn about the main features of this new stable release; or check the first beta release announcement to get t

29 may 2025, 9:10:17 | Symfony
Symfony 7.3 curated new features

Symfony 7.3.0 has been released. As for any other Symfony release, our backward compatibility promise applies and this means that you should be able to upgrade easily to 7.3 without changing anything

29 may 2025, 9:10:16 | Symfony
New in Symfony 7.3: DX Improvements (part 1)

Symfony 7.3 includes many small improvements aimed at making developers' lives easier and more productive. This blog post highlights some of the most useful DX (Developer Experience) features added in

28 may 2025, 9:50:15 | Symfony
New in Symfony 7.3: Validator Improvements

Symfony 7.3 introduces several enhancements to the Validator component, focusing on developer experience, better configurability, and more expressive constraint definitions.

Allow to Disable Translat

27 may 2025, 8:30:20 | Symfony