Pedro Cunha

:information_source: Laravel 11 now updates the timestamp when publishing vendor migrations. This may cause problems in existing applications when these migrations were previously published and ran with their default timestamp....

:warning: Previously, Laravel would append a colon (`:`) to any cache key prefix for DynamoDB, Memcache, or Redis. Laravel 11 no longer appends a colon to your cache key prefix....

:information_source: All of the underlying Symfony components used by Laravel have been upgraded to Symfony 7.0. Shift detected references to Symfony classes within your application. These are most likely type...

:warning: Laravel 11 requires PHP 8.2 or higher. You should verify the PHP version in your environments to ensure it meets this new requirement.

:warning: Laravel 11 now includes a database driver for MariaDB. Previously the MySQL driver offered parity with MariaDB. However, with MariaDB 10.1, there are more database specific features available. If...

:tada: Congratulations, you're now running the latest version of Laravel! Next, you may optionally run the following _Shifts_ to ensure your application is fully upgraded, adopts the latest Laravel conventions,...

Is there no global setting for it anymore then? Do you have to configure it per group?

Flying Saucer [requires Java 11 in 9.5.0, and Java 17 in 9.6.0](https://github.com/flyingsaucerproject/flyingsaucer?tab=readme-ov-file#getting-flying-saucer), so these changes are pending that, since we're still targeting Java 8.

This is indeed fixed in the `latest` documentation branch. `stable` is still pending that tag pushing you mentioned.

Is there any timeline or estimate on when a new tag will be pushed?