Laravel Cacheable Laravel Package

Getting Started

This release (1.12.0) is primarily a compatibility and maintenance release: it adds Laravel 11 and PHP 8.3 support, drops PHP 7.4, and refreshes dependencies and CI. Start by confirming your application’s runtime matrix:

• Laravel 11 requires PHP 8.2+, so pair it with PHP 8.2 or 8.3.
• Laravel 10 is still supported; PHP 8.1/8.2/8.3 are appropriate.
• PHP 7.4 is no longer supported — Composer will refuse to install 1.12.0 on PHP 7.4.

First steps:

1. Check composer.json for the package constraint and platform requirements.
2. Run composer require <vendor>/<package>:^1.12 (or update an existing constraint).
3. If the package publishes config or migrations, run php artisan vendor:publish and php artisan migrate as documented in the README.
4. Run your test suite before deploying; this release updates the package’s own PHPUnit configuration and test metadata, so treat it as a dependency bump that needs verification in your app.

Look first at the README and CHANGELOG for any package-specific upgrade notes. The release notes do not mention API changes, so the main first use case is upgrading an existing Laravel 10/PHP 8.1–8.2 app to Laravel 11/PHP 8.3 while keeping the package working.

Implementation Patterns

Upgrade workflow

• Update the package constraint to ^1.12, then run composer update <vendor>/<package> --with-dependencies.
• Run composer why-not <vendor>/<package> 1.12.0 if resolution fails; this usually reveals a PHP or Laravel platform conflict.
• Run the full test suite and any package-specific integration checks before merging.

CI matrix

If you maintain an application or downstream package that depends on this one, test against the supported matrix:

php: ['8.1', '8.2', '8.3']
laravel: ['10.*', '11.*']

Exclude incompatible combinations (for example, Laravel 11 with PHP 8.1). This mirrors the package’s own updated GitHub Actions workflow.

Test metadata

The package moved its tests from doc-comment metadata to PHP 8 attributes. If you extend or copy its test patterns, prefer attributes such as #[DataProvider] and #[Test] over annotations. This is internal to the package, but it signals that the codebase now assumes PHP 8+ syntax.

Integration tips

• If the package uses Laravel auto-discovery, no service provider registration is needed. On Laravel 11, verify discovery still works after upgrading.
• If you publish config, diff your published config against the new package default after upgrading.
• Pin the package to ^1.12 in applications that need Laravel 11 support; older constraints may resolve to a version that does not support it.

Gotchas and Tips

• Dropping PHP 7.4 is a breaking platform change. Applications still on PHP 7.4 cannot install 1.12.0. Either upgrade PHP or stay on the previous package release.
• Laravel 11 skeleton differences. Laravel 11 removed some default files and changed provider registration (bootstrap/providers.php). If the package relies on manual provider registration, confirm the documented steps still apply.
• Dependency updates may surface transitive conflicts. The release updates package dependencies; run composer update --with-all-dependencies and check for conflicts with your app’s pinned packages.
• PHPUnit configuration changes are package-internal. They should not affect consumers, but if you reuse the package’s test setup, align your PHPUnit version and configuration.
• Debugging resolution failures: use composer why-not, composer show --platform, and composer diagnose. Most install failures after this release will be PHP version or Laravel framework constraint mismatches.
• Extension points: check the README for published config, container bindings, events, and macros. This release does not advertise new extension points, so existing customization should continue to work — but verify after upgrading.
• No documented API removals. The release notes list no deprecations or removed methods beyond PHP 7.4 support. Still, run your integration tests; maintenance releases can include dependency-driven behavior changes.