Symfony 7.1.3 released

July 26, 2024 • Published by Avatar of Fabien Potencier Fabien Potencier

Symfony 7.1 is backed by:

Les-Tilleuls.coop is a team of 70+ Symfony experts who can help you design, develop and fix your projects. We provide a wide range of professional services including development, consulting, coaching, training and audits. We also are highly skilled in JS, Go and DevOps. We are a worker cooperative!
At Rector, we help successful and growing companies to get the most of the code they already have. Including upgrading to the latest Symfony LTS. We deliver automated refactoring, reduce maintenance costs, speed up feature delivery, and transform legacy code into a strategic asset. Let us handle the dirty work, so you can focus on the features.
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.

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

  • bug #57803 [FrameworkBundle] move adding detailed JSON error messages to the validate phase (@xabbuh)
  • bug #57815 [Console][PhpUnitBridge][VarDumper] Fix NO_COLOR empty value handling (@alexandre-daubois)
  • bug #57828 [Translation] Fix CSV escape char in CsvFileLoader on PHP >= 7.4 (@alexandre-daubois)
  • bug #57812 [Validator] treat uninitialized properties referenced by property paths as null (@xabbuh)
  • bug #57816 [DoctrineBridge] fix messenger bus dispatch inside an active transaction (@IndraGunawan)
  • bug #57799 [ErrorHandler][VarDumper] Remove PHP 8.4 deprecations (@alexandre-daubois)
  • bug #57772 [WebProfilerBundle] Add word wrap in tables in dialog to see all the text in workflow listeners dialog (@SpartakusMd)
  • bug #57708 [PropertyInfo] Check if property is nullable when using ReflectionExtractor (@benjilebon)
  • bug #57802 [PropertyInfo] Fix nullable value returned from extractFromMutator on CollectionType (@benjilebon)
  • bug #57832 [DependencyInjection] Do not try to load default method name on interface (@lyrixx)
  • bug #57748 [SecurityBundle] use firewall-specific user checkers when manually logging in users (@xabbuh)
  • bug #57753 [ErrorHandler] restrict the maximum length of the X-Debug-Exception header (@xabbuh)
  • bug #57646 [Serializer] Raise correct exception in ArrayDenormalizer when called without a nested denormalizer (@derrabus)
  • bug #57674 [Cache] Improve dbindex DSN parameter parsing (@constantable)
  • bug #57678 [Validator] Add setGroupProvider to AttributeLoader (Maximilian Zumbansen)
  • bug #57679 [WebProfilerBundle] Change incorrect check for the stateless request attribute (@themasch)
  • bug #57663 [Cache] use copy() instead of rename() on Windows (@xabbuh)
  • bug #57617 [PropertyInfo] Handle collection in PhpStan same as PhpDoc (@mtarld)
  • bug #54057 [Messenger] Passing actual Envelope to WorkerMessageRetriedEvent (@daffoxdev)
  • bug #57645 [Routing] Discard in-memory cache of routes when writing the file-based cache (@mpdude)
  • bug #57621 [Mailer] force HTTP 1.1 for Mailgun API requests (@xabbuh)
  • bug #57616 [String] Revert "Fixed u()->snake(), b()->snake() and s()->snake() methods" (@nicolas-grekas)
  • bug #57593 [SecurityBundle] Compare paths after realpath() has been applied to both (@xabbuh)
  • bug #57594 [String] Normalize underscores in snake() (@xabbuh)
  • bug #57585 [HttpFoundation] Fix MockArraySessionStorage to generate more conform ids (@Seldaek)
  • bug #57589 [FrameworkBundle] fix AssetMapper usage without assets enabled (@xabbuh)

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

Comments are closed.

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