Laravel 13 support and a platform upgrade

The client package now runs on Laravel 10 to 13, and the Eloquentize app itself has been upgraded to Laravel 13 and Filament 5.

The client package: Laravel 10 to 13

A new version of eloquentize/laravel-eloquentize-client is out. It is tested against Laravel 10, 11, 12 and 13, including the lowest and highest versions each of them allows, so the package keeps working whichever Laravel version your application runs.

To update:

Nothing changes in your configuration or in the commands you already schedule.

Fixes in the commands

While adding the new versions to our test matrix, we reviewed how the commands behave when something is wrong. A few things are now handled properly:

• Invalid model or property: eloquentize:property-aggregate and eloquentize:property-aggregate-overall no longer send a meaningless value to Eloquentize. They stop, print an error, and exit with a failure code.
• Invalid date: a date that does not match the expected format (d/m/Y by default, or the one you set with --dateFormat) is rejected with a clear message instead of ending in a PHP error. This also covers Carbon 3, which reports malformed dates differently.
• Invalid aggregation: an unknown aggregation (anything other than min, max, avg or sum) no longer stops the whole PHP process. It reports the error and returns a failure code, so a scheduled run cannot take your application down with it.

One consequence to be aware of: these commands now return a non-zero exit code in those cases. If you monitor your scheduler, such a run will show up as failed, which is the point.

The Eloquentize app

The platform itself has been moved to Laravel 13 and Filament 5, with the front-end rebuilt on Tailwind CSS 4. You should not notice much, apart from a few things:

• The dashboard and the widgets share the same look as before, on updated foundations.
• The chart filters (period type and date range) were rebuilt on the new Filament filters API.
• Admin monitoring now relies on the official Laravel Pulse.

If something looks off on your dashboard after the update, let us know and we will fix it.

The documentation is up to date with the current version of the package.