« Living on the edge » blog posts
Filter posts by Symfony release
Symfony 5.0 and 4.4 have the same new features because both were released at the same time. Learn more about the Symfony release process.
New in Symfony 4.4: PHPUnit Polyfills
Symfony 4.4 will provide several polyfills for PHPUnit so you can use the same tests with different versions of PHP and PHPUnit.
New in Symfony 4.4: Notification Emails
Symfony 4.4 will include a feature to create notification emails, which are standardized messages intended to send notifications to yourself.
New in Symfony 4.4: Encrypted Secrets Management
Symfony 4.4 will include a new feature to manage encrypted secrets, which is useful to store sensitive configuration values such as passwords, tokens, certificates, etc.
New in Symfony 4.4: Simpler Event Listeners
In Symfony 4.4, event listeners no longer require to define the event name in the service configuration and Doctrine entity listeners added support for __invoke() methods.
New in Symfony 4.4: Redis Cache Improvements
Symfony 4.4 will add support for Redis Sentinel and it will improve the Redis tag-aware cache to consume less memory and support up to 4 billion keys per tag.
New in Symfony 4.4: Horizontal Tables and Definition Lists in Console Commands
In Symfony 4.4, commands will add new ways of displaying tabular data: horizontal tables and definition lists.
New in Symfony 4.4: Improved Welcome Page
In Symfony 4.4, the Welcome Page displayed when you haven't configured any URL, has been revamped to show a better design and more useful resources.
New in Symfony 4.4: Password Migrations
In Symfony 4.4, user passwords can be rehashed automatically when a better hashing algorithm is available.
New in Symfony 4.4: PHPUnit Assertions for Email Messages
In Symfony 4.4, you can use new PHPUnit assertions to test the email messages and their contents.
New in Symfony 4.4: Messenger Middleware to Clear Doctrine Entity Manager
In Symfony 4.4, the Messenger component added a new middleware to clear the Doctrine entity manager when a message is consumed to avoid memory leaks and side-effects.