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

Établi 3y | 1 mai 2022, 18:20:18


Connectez-vous pour ajouter un commentaire

Autres messages de ce groupe

A Week of Symfony #973 (August 18–24, 2025)

This week, Symfony development focused on improving the IsGranted attribute with a new option, updated the Route attribute to allow setting multiple environments, improved the DomCrawler component to

24 août 2025, 09:40:28 | Symfony
A Week of Symfony #972 (August 11–17, 2025)

This week, development activity mostly focused on dealing with the deprecation of sleep/wakeup methods in PHP 8.5 and their replacement by serialize/unserialize methods. In addition, we published more

17 août 2025, 08:30:06 | Symfony
Let’s build the Symfony AI ecosystem together

It’s been only in July that we published symfony/ai and kicked off our AI initiative, but the repository has been busy since day one. Over 500 stars, more than 200 pull requests & issues, trending

16 août 2025, 09:30:03 | Symfony
SymfonyCon Amsterdam 2025:   Unconference Track at SymfonyCon Amsterdam 2025

🎤 Take the stage at SymfonyCon Amsterdam 2025, on your own terms!

The Unconference track is back and more dynamic than ever!

This unique, participant-driven format invites attendees to shape

12 août 2025, 12:40:20 | Symfony
A Week of Symfony #971 (August 4–10, 2025)

This week, Symfony completed the migration to PHPUnit 12 in the 7.4 branch, which required many changes during the past weeks, such as replacing annotations with attributes. In addition, we updated th

10 août 2025, 09:40:09 | Symfony
SymfonyCon Amsterdam 2025:  Join the Symfony Hackathon:  Collaborate, Contribute, Create

🧑‍💻HACKDAY IS COMING!

Get ready to code, collaborate, and contribute, Symfony Hackday is back!

Join us in Amsterdam on Saturday, November 29th, for a hands-on hackathon designed to bring the

6 août 2025, 10:40:04 | Symfony
A Week of Symfony #970 (July 28 – August 3, 2025)

This week, Symfony released the maintenance versions 6.4.24, 7.2.9, and 7.3.2. Meanwhile, we began deprecating the XML configuration format in some components, enhanced the YAML configuration format t

3 août 2025, 08:30:03 | Symfony