Symfony 4.4.33 has just been released. Here is a list of the most important changes: bug #43798 [Dotenv] Duplicate $_SERVER values in $_ENV if they don't exist (@fancyweb) bug #43799 [PhpUnitBridge] fix symlink to bridge in docker by making its path relative (@nicolas-grekas) bug #43781 [Messenger] Fix TraceableMessageBus implementation so it can compute caller even when used within a callback (@Ocramius) bug #43655 [VarDumper] Fix dumping twig templates found in exceptions (@event15) bug #43484 [Messenger] Fix Redis Transport when username is empty (@villfa) bug #43568 [Messenger] fix: TypeError in PhpSerializer::encode() (@dsech) bug #43591 [Config] Fix files sorting in GlobResource (@lyrixx) bug #43569 [HttpClient] fix collecting debug info on destruction of CurlResponse (@nicolas-grekas) bug #43545 [DependencyInjection] fix "url" env var processor (@nicolas-grekas) bug #43413 [VarDumper] Fix error with uninitialized XMLReader (@villfa) bug #43388 [Validator] Fixes URL validation for single-char subdomains (@DfKimera) bug #43333 [HttpClient] fix missing kernel.reset tag on TraceableHttpClient services (@nicolas-grekas) bug #43302 [Cache] Commit items implicitly only when deferred keys are requested (@Sergey Belyshkin) bug #43330 [Cache][Lock] fix SQLSRV throws for method_exists() (@GDmac) bug #43270 [VarDumper] Fix handling of "new" in initializers on PHP 8.1 (@nicolas-grekas) bug #43277 [DependencyInjection] fix support for "new" in initializers on PHP 8.1 (@nicolas-grekas) bug #43243 [HttpClient] accept headers when CURLE_RECV_ERROR is received before the content (@nicolas-grekas) bug #43205 [Serializer] Fix denormalizing XML array with empty body (4.4) (@alexandre-daubois) 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.
Sponsor the Symfony project.
http://feedproxy.google.com/~r/symfony/blog/~3/0y2B6gc_3Qg/symfony-4-4-33-released
Zaloguj się, aby dodać komentarz
Inne posty w tej grupie

This week, development activity focused on putting the final touches on Symfony 7.3 in preparation for its stable release next week. In addition, we published a security fix for a potential vulnerabil

Symfony's bridge packages integrate third-party services, such as mailers, notifiers, and translation providers, into Symfony applications. With more than 120 bridges available today, Symfony supports

Symfony Messenger component keeps evolving to meet the needs of complex, modern applications. In Symfony 7.3, we're introducing several powerful features to it.
Run Process Using the Shell… https://s

The Routing component provides an impressive list of features to map incoming URLs to your application code. Symfony 7.3 pushes it even further with a set of new features that improve developer experi

Contributed by Mathias Arlaud in

Affected versions
Symfony UX symfony/ux-live-component and symfony/ux-twig-component versions <2.25.1 are affected by this security issue.
The issue has been fixed in the 2.25.1 version of these

Symfony has been reducing the need for configuration in applications for several years now. Thanks to PHP attributes, you can now configure most things alongside the relevant code, removing the need f