Symfony 7.1.1 has simply been launched.
Right here is the listing of crucial modifications since 7.1.0:
- bug #57110 [PhpUnitBridge] Repair error handler triggered outdoors of exams (@HypeMC)
- bug #57305 [Validator] don’t modify a constraint throughout validation to not leak its context (@xabbuh)
- bug #57297 [FrameworkBundle] not registered definitions should not be modified (@xabbuh)
- bug #57234 [String] Repair Inflector for ‘{hardware}’ (@podhy)
- bug #57224 [Mime] Use streams as a substitute of loading uncooked message generator into reminiscence (@bytestream)
- bug #57284 [Mime] Repair TextPart utilizing an unknown File (@fabpot)
- bug #57282 [Scheduler] Throw an exception when no dispatcher has been handed to a Schedule (@fabpot)
- bug #57276 Repair autoload configs to keep away from warnings when constructing optimized autoloaders (@Seldaek)
- bug #57275 Repair autoload configs to keep away from warnings when constructing optimized autoloaders (@Seldaek)
- bug #57263 [SecurityBundle] Repair container.build_hash parameter binding (@alexandre-daubois)
- bug #57197 [Serializer] Repair denormalizing a group of union varieties (@HypeMC)
- bug #57188 [DoctrineBridge] Repair UniqueEntityValidator with proxy object (@HypeMC)
Need to improve to this new launch? As a result of Symfony protects
backwards-compatibility very carefully, this ought to be fairly straightforward. Use
SymfonyInsight improve experiences
to detect the code you have to to alter in your venture and
learn our improve
documentation to be taught extra.
Need to be notified every time a brand new Symfony launch is printed? Or when a
model is just not maintained anymore? Or solely when a safety challenge is fastened?
Take into account subscribing to the Symfony Roadmap Notifications.
