Symfony 4.4.15 has just been released with a good list changes, but also with a warning that it could break your application if you’ve already updated your dependencies to the latest patch versions and if you started using the new src/preload.php file. Fabien Potencier noted in the announcement :
Unfortunately, we quickly discovered that it was a problem for many users just after the release, so we’ve then decided to revert it in favor of a
config.preload.phpfile generated via a recipe.
List of changes included in this release including the revert bug issue :
- [Lock] Fix StoreFactory to accept same DSN syntax as AbstractAdapter
- [Serializer][Minor] Fix circular reference exception message (bad limit displayed)
- [HttpClient] Always “buffer” empty responses
- [Form] propagate validation groups to subforms
- Ignore more deprecations for Mockery mocks
- [HttpClient] fix using proxies with NativeHttpClient
- [Routing] fix using !important and defaults/reqs in inline route definitions
- ErrorHandler][DebugClassLoader] Do not check Mockery mocks classes
- [HttpClient] Fix using https with proxies
- [TwigBundle] Only remove kernel exception listener if twig is used
- [BrowserKit] Cookie expiration at current timestamp
- [Messenger] Fix redis connection error message
- Revert “bug #38063 [FrameworkBundle] generate preload.php in src/ to make opcache.preload predictable”
- PhpUnitBridge] Fixed clas _alias() for PHPUnitFrameworkErrorError
Almost the same changes in the 5.1.7 in addition to the revert bug and the few issues below :
- Handle consecutive supports() calls in the RememberMeAuthenticator
- [PhpUnitBridge] Fix Deprecation file when it comes from the TestsListener
- [DI] fix dumping non-shared lazy services
- [FrameworkBundle] Add Mailjet definition
Of course you are not encouraged to upgrade but obliged to, just one week after the release of 4.4.14 and 5.1.6, but things like that could happens.
