13.7.0

tablar:update now actually updates your packages. If you have an existing app, this is the release worth taking.

Fixed

• tablar:update could not change any of Tablar's own npm packages. The installer merged Tablar's pinned versions first and your package.json second, and because the keys are strings the second array won, so whatever you already had stayed. @tabler/core, bootstrap, @popperjs/core and around twenty plugins were frozen at their original versions no matter how many times you ran the command. Only the handful of packages that get stripped before the merge, such as vite and axios, ever moved. Tablar's versions now win, and packages you added yourself are still left alone.
• tablar:install published its migrations but did not tell you to run them, while also adding the SoftDeletes trait to your User model. Following the printed steps gave a 500 with Unknown column 'users.deleted_at' as soon as someone registered. php artisan migrate is now the first step it prints.

Changed

• tablar:update wires itself to the console the same way tablar:install does, and takes a --force flag. Nothing in the update path overwrites files you have edited today, so the flag has no effect yet; it is there for when it does.
• The bundled install skill for Laravel Ajax Builder now refers to TakiElias\Lab, following the namespace change in takielias/lab 1.2.0. Old imports still work there.

Upgrading

composer update takielias/tablar
php artisan tablar:update
npm install && npm run build

Verified on a clean install: with @tabler/core pinned at 1.0.0 and bootstrap at 5.2.0, tablar:update moved them to 1.4.0 and 5.3.8 and left an unrelated package alone.

Requires PHP 8.3+, Laravel 12 or 13, Node 20.19+.