Symfony 5.3.9 released

September 28, 2021 · Published by Avatar of Fabien Potencier Fabien Potencier

Symfony 5.3 is backed by:

JoliCode is a team of passionate developers and open-source lovers, with a strong expertise in PHP & Symfony technologies. They can help you build your projects using state-of-the-art practices.

Warning: Symfony 5.3 is no longer supported. Consider upgrading your applications to the most recent Symfony version.

Symfony 5.3.9 has just been released. Here is a list of the most important changes:

Want to upgrade to this new release? Because Symfony protects backwards-compatibility very closely, this should be quite easy. Use SymfonyInsight upgrade reports to detect the code you will need to change in your project and read our upgrade documentation to learn more.

Want to be notified whenever a new Symfony release is published? Or when a version is not maintained anymore? Or only when a security issue is fixed? Consider subscribing to the Symfony Roadmap Notifications.

Published in #Releases

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

Comments

Avatar of RERBAL
RERBAL said on Sep 28, 2021
Hello!
thanks for this release, but the "list of the most important changes" is empty. could you please tell us more about it?
Avatar of Renan Lazarotto
Renan Lazarotto said on Sep 28, 2021
@RERBAL: https://github.com/symfony/symfony/pull/43230/commits/6a61bcb95eb6b36036866d0d0f0940738d3fb9a1
Avatar of RERBAL
RERBAL said on Sep 28, 2021
@Renan, Thx ! it was repported on the git too, i'dont get what was the issue exactly but i'll wait some more detail to run the update
Avatar of Wouter de Jong
Wouter de Jong said on Sep 28, 2021
@RERBAL there was a bug in the internal tool that splits the main symfony/symfony repository into separate repositories (per package) after a release (caused by an update of a dependency).

As with any bugs in the release tooling of Symfony in the past, I'm sure this incident will result in even more safety checks during the release process. But as we - as developers - know, there will always be a bug sometime somewhere in any code that is evolving.

The two incorrect releases of this morning have been removed from GitHub and Packagist, so it is as safe as always to upgrade to the latest versions ever since 5.3.9 and 4.4.32 were released.
Avatar of RERBAL
RERBAL said on Sep 29, 2021
@Wouter
thanks a lot for the explaintion, i was just curious about the fact that I didn't remember seen any auther SensioLabs article with empty phrase like this one, also i'll follow the advice with this 5.3.9 release and furthers in the future... Thx!

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.