Getting Started

Install with composer require at ^3.3. Before upgrading, check your app's Laravel version: 3.3.0 supports Laravel 12 and 13, and drops Laravel 11. On Laravel 11, pin to the latest 3.2.x instead.
First place to look is the package's composer.json (require/conflict constraints) and README install section — this release is a support-matrix change, so confirm your laravel/framework and php constraints line up before running composer update.
First use case: treat 3.3.0 as your Laravel 13 adoption path. If you're planning a Laravel 12 → 13 upgrade, bump this package in the same branch so you're not debugging two upgrade surfaces at once.
If you were already on 3.2.x with Laravel 12, upgrading is a low-risk patch bump: pull it in, run your test suite, and confirm no PHPStan regressions.

Implementation Patterns

Version-gated upgrades. Keep Laravel 11 apps on ^3.2 and only move to ^3.3 after the framework upgrade lands. Use separate branches/PRs for "framework upgrade" and "package upgrade" so failures are attributable.
CI matrix alignment. If you test across multiple Laravel versions, drop the Laravel 11 leg from your matrix when you adopt 3.3.0, and add a Laravel 13 leg. A matrix that still includes 11 will fail at dependency resolution, not at test time — resolve that first.
Static analysis in the same pass. Since 3.3.0 fixes PHPStan typing, re-run PHPStan at your configured level after upgrading. If you had baseline entries suppressing type errors originating in this package, try removing them — the underlying types should now be correct.
Test-harness consistency. The release also fixes testing errors. If you maintain test helpers or fixtures around this package, re-run your suite and clear cached artifacts (config/route/compiled caches) before assuming a regression is yours.
Lockstep deployments. Bump the package and deploy in the same release cycle as the framework version, rather than letting the app run ahead of or behind the package's supported matrix.

Laravel 11 is a hard break. composer update will fail with a constraint conflict rather than a friendly message. Read the constraint error before downgrading other packages — the fix is usually to pin this package to ^3.2, not to fight the resolver.
Laravel 13 support is new. Expect transitive dependencies (testing tools, dev utilities, static analysis packages) to lag. If resolution fails on a sibling package, it's often not this package's constraint but a neighbour that hasn't shipped Laravel 13 support yet.
PHPStan type fixes can shift your baseline. Docblock/annotation changes are source-compatible but may alter inferred types. If your own code relied on the previously loose types, you may see new errors — treat those as genuine signal, not noise.
Clear caches after upgrading. Run php artisan config:clear, route:clear, view:clear, and composer dump-autoload before debugging anything, especially if the package ships a service provider or publishable config.
Pin in composer.json, don't float. Use ^3.3 rather than * or a dev branch so a future major doesn't silently change your support matrix.
Check the changelog before every minor bump. This package signals support changes through minor releases, so a 3.3 → 3.4 bump can drop an older Laravel version without a major-version warning.