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: 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
New in Symfony 7.3: Serializer Improvements

Symfony 7.3 adds a new JsonStreamer component as a high-performance, low-memory JSON encoding and decoding utility. However, the Serializer component still has many valid use cases, even for JSON cont

26 may 2025, 9:20:09 | Symfony
Symfony 7.3.0-RC1 released

Symfony 7.3.0-RC1 has just been released. This is a pre-release version of Symfony 7.3. If you want to test it in your own applications before its final release, run the following commands:

26 may 2025, 0:10:10 | Symfony
A Week of Symfony #960 (May 19–25, 2025)

This week, development activity focused on putting the final touches on Symfony 7.3 in preparation for its stable release next week. In addition, we published a security fix for a potential vulnerabil

25 may 2025, 10:10:12 | Symfony
New in Symfony 7.3: New Bridges and Improved Integrations

Symfony's bridge packages integrate third-party services, such as mailers, notifiers, and translation providers, into Symfony applications. With more than 120 bridges available today, Symfony supports

23 may 2025, 9:30:04 | Symfony
New in Symfony 7.3: Messenger Improvements

Symfony Messenger component keeps evolving to meet the needs of complex, modern applications. In Symfony 7.3, we're introducing several powerful features to it.

Run Process Using the Shell… https://s

22 may 2025, 7:50:11 | Symfony
New in Symfony 7.3: Routing Improvements

The Routing component provides an impressive list of features to map incoming URLs to your application code. Symfony 7.3 pushes it even further with a set of new features that improve developer experi

21 may 2025, 11:10:07 | Symfony