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

Back on the inspiring SymfonyCon Vienna 2024!

We were absolutely thrilled to gather with the incredible Symfony community for the first time in Vienna, Austria, from December 5th to 6th, surrounded by the warm and festive atmosphere of the

31 janv. 2025 à 12:30:18 | Symfony
SymfonyLive Paris 2025 : Reveal of workshop topics!

SymfonyLive Paris 2025, conference in French language only, will take place from March 27 to 28! The schedule is currently being revealed as we go along. More details are available here.

💻

30 janv. 2025 à 08:50:03 | Symfony
Get Symfony news on your favorite social network

Symfony has been active on X, Mastodon, and Bluesky for some time, but until recently, not all platforms received equal attention. Since Twitter (now X) was our first social network, all blog posts we

29 janv. 2025 à 14:20:10 | Symfony
SymfonyLive Berlin 2025: Demystify the magic of the Container

SymfonyLive Berlin 2025, conference held in English, will take place from April 1 to 4! The schedule is being revealed gradually. More details are available here.

As we are now unveiling th

29 janv. 2025 à 14:20:10 | Symfony
Twig CVE-2025-24374: Missing output escaping for the null coalesce operator

Affected versions

Twig versions >=3.16.0,<3.19.0 are affected by this security issue.

The issue has been fixed in Twig 3.19.0.

Description

When using the null coalesce operator (??), output esc

29 janv. 2025 à 09:40:06 | Symfony
Symfony 6.4.18 released

Symfony 6.4.18 has just been released. Here is the list of the most important changes since 6.4.17:

bug #58889 [Serializer] Handle default context in Serializer (@Valmonzo)

bug #59631 [HttpClient

29 janv. 2025 à 09:40:05 | Symfony
Symfony 7.1.11 released

Symfony 7.1.11 has just been released. Here is the list of the most important changes since 7.1.10:

bug #58889 [Serializer] Handle default context in Serializer (@Valmonzo)

bug #59631 [HttpClient

29 janv. 2025 à 09:40:05 | Symfony