Symfony 4.4.46 has simply been launched.
Right here is the listing of an important adjustments since 4.4.45:
- bug #47547 [Ldap] Don’t run ldap_set_option on failed connection (@tatankat)
- bug #47578 [Security] Repair AbstractFormLoginAuthenticator return sorts (@AndrolGenhald)
- bug #47614 [FrameworkBundle] Repair a phpdoc in mailer assertions (@HeahDude)
- bug #47516 [HttpFoundation] Forestall BinaryFileResponse::put together from including content material sort if no content material is distributed (@naitsirch)
- bug #47533 [Messenger] decode URL-encoded characters in DSN’s usernames/passwords (@xabbuh)
- bug #47530 [HttpFoundation] At all times return strings from settle for headers (@ausi)
- bug #47497 [Bridge] Repair mkdir() race situation in ProxyCacheWarmer (@andrey-tech)
- bug #47415 [HttpClient] Psr18Client ignore invalid HTTP headers (@nuryagdym)
- bug #47435 [HttpKernel] lock when writting profiles (@nicolas-grekas)
- bug #47437 [Mime] Repair e mail rendering when having inlined elements that aren’t associated to the content material (@fabpot)
- bug #47434 [HttpFoundation] transfer flushing exterior of Response::closeOutputBuffers (@nicolas-grekas)
- bug #47351 [FrameworkBundle] Don’t throw when describing a manufacturing unit definition (@MatTheCat)
- bug #47403 [Mailer] Repair edge instances in STMP transports (@fabpot)
Wish to improve to this new launch? As a result of Symfony protects
backwards-compatibility very intently, this must be fairly straightforward. Use
SymfonyInsight improve experiences
to detect the code you’ll need to alter in your mission and
learn our improve
documentation to be taught extra.
Wish to be notified at any time when a brand new Symfony launch is revealed? Or when a
model is just not maintained anymore? Or solely when a safety concern is fastened?
Think about subscribing to the Symfony Roadmap Notifications.
