Nova Field Mixins Laravel Package

Getting Started

This release (v3.0.1) is a compatibility patch: it adds support for Laravel Framework 12. No new APIs are introduced, so the primary reason to move to this version is to run the package on a Laravel 12 application.

1. Confirm version constraints. Check the package's composer.json for illuminate/* and php requirements. Laravel 12 requires PHP 8.2+, so ensure your app meets that before updating.
2. Install or upgrade.

   composer require <vendor>/<package>:^3.0
   # or, if already installed
   composer update <vendor>/<package> --with-dependencies
   

3. Verify registration. Most Laravel packages auto-discover their service provider. If the README lists a manual provider/facade entry, confirm it is present in bootstrap/providers.php (Laravel 11+/12 style) rather than the legacy config/app.php.
4. Publish assets if needed. Run php artisan vendor:publish --provider="<Vendor>\<Package>\<Package>ServiceProvider" and review the published config before changing defaults.
5. First use case. Run the package's own test suite or a smoke test against a fresh Laravel 12 skeleton (e.g. orchestra/testbench) to validate the integration before wiring it into application code.

Where to look first: the package README, composer.json platform constraints, the changelog, and the service provider's register()/boot() methods to understand what is bound into the container.

Implementation Patterns

• Upgrade path in CI. Add a Laravel 12 job to your matrix alongside existing versions. Because this is a patch release, tests should pass without code changes; failures usually indicate an indirect dependency still pinned below Laravel 12.
• Pin the constraint, not the lockfile. Use "<vendor>/<package>": "^3.0" in composer.json and let the lockfile resolve. Avoid hard-pinning 3.0.1 unless you need reproducibility across environments.
• Service provider as the integration seam. Resolve package behaviour through the container (constructor injection or app()->make()) rather than static calls, so you can swap or mock it in tests.
• Config-driven setup. Prefer publishing and editing the config file over modifying vendor code; keep environment-specific values in .env and reference them from the config.
• Testbench for package-adjacent tests. If you extend or wrap the package, use orchestra/testbench with a Laravel 12 test case to exercise it under the same framework version.
• Gradual rollout. Deploy to a staging environment on Laravel 12 first, run php artisan config:clear and php artisan cache:clear, then promote.

Gotchas and Tips

• Patch release, but framework-major. 3.0.1 only widens framework compatibility, but Laravel 12 itself brings changes (PHP 8.2 minimum, updated skeleton conventions, deprecated APIs). Read the Laravel 12 upgrade guide alongside this release.
• Dependency conflicts. If composer update fails, it is almost always a transitive dependency pinning illuminate/* to ^10 or ^11. Inspect with composer why-not <vendor>/<package> 3.0.1 before forcing anything.
• Don't assume API stability from the version number. Verify the changelog for any changes between the version you were on and 3.0.1 — the notes here only mention Laravel 12, so re-check the full release history if you are jumping from 2.x.
• Config and route caching. After upgrading, run php artisan optimize:clear; stale cached config is a common cause of "works locally, fails in CI" issues with packages.
• Service provider discovery cache. If the provider is not loading on Laravel 12, check bootstrap/cache/packages.php and run composer dump-autoload followed by php artisan package:discover.
• Extension points. Prefer the package's published config, events, and container bindings for customisation. If you must override behaviour, bind your own implementation in a service provider rather than editing vendor files.
• Report issues upstream. Because Laravel 12 support is the whole point of this release, any incompatibility you hit is likely a bug worth filing with a minimal reproduction on a fresh Laravel 12 app.