Symfony Blog

Today, December 31, 2019, is the last day of the 2010s decade. That's why it's the perfect moment to make a quick recap of the last 10 years for the Symfony project.

The end of the year is the best time to review all that we achieved as a community during the past twelve months. These are some of the highlights of the 2019 year for the Symfony Project.

This week, Symfony 4.4 migrated the server:log command away from the deprecated WebServerBundle. Meanwhile, the upcoming Symfony 5.1 version merged several performance improvements, such as adding an array cache in front of the serializer cache. In addition, it improved developer experience when using Search, Email and Tel form types.

This week, Symfony 4.4.2 and 5.0.2 maintenance versions were released. Meanwhile, we improved performance when using Symfony with the Alpine Linux distribution, which is common when using Docker.

Read release notes

Read release notes

Symfony 5.0 introduces a new String component which deals with bytes, UTF-8 code points and grapheme clusters in a unified way, provides an object-oriented API for strings, and includes a slugger.

Symfony 4.4 improves the password hashing and migration features, provides faster container compilation, simplifies the redirection config in YAML and makes exceptions easier to understand when running tests.

In Symfony 4.4, routing config can exclude patterns, checking HTML contents is easier in tests, expressions support scientific numeric format, isGranted() deprecated checking multiple permissions and Twig linter included new options.

Symfony 4.4 adds many useful improvements, such as better PropertyAccess error messages, support for more only-of-type CSS selectors, a more flexible Range constraint, the option to sort extracted translation messages, an option to consider empty strings invalid and gitattributes files to exclude tests.