Adminix Documentation Help

Upgrade and Changelog

Current stabilization notes

This release line focuses on package stabilization and safer defaults.

Changed

  • Laravel service provider is auto-discovered through Composer metadata.

  • Default package config no longer references application-specific App\Adminix\Pages classes.

  • adminix:install publishes config, assets, and optional examples.

  • make:adminix_resource creates a starter resource page provider.

  • Save and create controllers derive dataSource, primary key, and writable fields from server-side module configuration.

  • Search uses ILIKE only on PostgreSQL and LIKE on other drivers.

  • Search escapes LIKE wildcards and caps query length before applying filters.

  • Soft-deleted updates call withTrashed() only for Eloquent models that use SoftDeletes.

  • Composer package scripts no longer run Laravel app-only Artisan commands from the package root.

  • Compact Laravel Boost guidelines and skill resources are available for parent projects.

  • Public asset publishing now includes only Adminix runtime JavaScript and CKEditor 5 runtime files.

  • Resource IMAGE fields are writable URL/path inputs; resource JSON fields are writable textareas.

  • Page catch-all routing is GET-only; save/create operations stay on explicit POST routes.

  • Stored upload fields reject scalar path submissions on update; upload paths change only through real files or allowed remove checkboxes.

  • make:adminix_resource --model rejects invalid PHP class names before dry-run output or file generation.

Compatibility

Supported constraints are declared in composer.json:

  • PHP >=8.2;

  • Laravel ^12.0|^13.0;

  • Symfony HTTP Foundation ^6.3|^7.0|^8.0.

CI now only builds and publishes the Writerside documentation pages. Run PHPUnit, coverage threshold checks, and PHP/Laravel compatibility checks locally before release-sensitive upgrades.

Upgrade checklist

  1. Run composer update alex-kudrya/adminix.

  2. Publish new assets with php artisan adminix:install --force.

  3. If your app published assets before v2.0.7, remove stale public/js/adminix/ckeditor and public/css/adminix/ckeditor.css after republishing.

  4. Check config/adminix.php; explicitly configure pages. Empty menu.links is valid for initial setup.

  5. Keep no_auth_access disabled outside local/demo environments.

  6. Run your application test suite around Adminix CRUD pages and modal forms.

Last modified: 22 June 2026