Symfony 7.1.10 has just been released. Here is the list of the most important changes since 7.1.9:
- bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario Guarracino)
- bug #59228 [HttpFoundation] Avoid mime type guess with temp files in BinaryFileResponse (@alexandre-daubois)
- bug #59318 [Finder] Fix using == as default operator in DateComparator (@MatTheCat)
- bug #59321 [HtmlSanitizer] reject URLs containing whitespaces (@xabbuh)
- bug #59250 [HttpClient] Fix a typo in NoPrivateNetworkHttpClient (@Jontsa)
- bug #59103 [Messenger] ensure exception on rollback does not hide previous exception (@nikophil)
- bug #59226 [FrameworkBundle] require the writer to implement getFormats() in the translation:extract (@xabbuh)
- bug #59213 [FrameworkBundle] don't require fake notifier transports to be installed as non-dev dependencies (@xabbuh)
- bug #59066 Fix resolve enum in string type resolver (@DavidBadura)
- bug #59156 [PropertyInfo] Fix interface handling in PhpStanTypeHelper (@mtarld)
- bug #59160 [BeanstalkMessenger] Round delay to an integer to avoid deprecation warning (@plantas)
- bug #59012 [PropertyInfo] Fix interface handling in PhpStanTypeHelper (@janedbal)
- bug #59134 [HttpKernel] Denormalize request data using the csv format when using "#[MapQueryString]" or "#[MapRequestPayload]" (except for content data) (@ovidiuenache)
- bug #59140 [WebProfilerBundle] fix: white-space in highlighted code (@chr-hertel)
- bug #59124 [FrameworkBundle] fix: notifier push channel bus abstract arg (@raphael-geffroy)
- bug #59069 [Console] Fix division by 0 error (@Rindula)
- bug #59070 [PropertyInfo] evaluate access flags for properties with asymmetric visibility (@xabbuh)
- bug #59062 [HttpClient] Always set CURLOPT_CUSTOMREQUEST to the correct HTTP method in CurlHttpClient (@KurtThiemann)
- bug #59023 [HttpClient] Fix streaming and redirecting with NoPrivateNetworkHttpClient (@nicolas-grekas)
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.