chore: drop Laravel 11 support - #21
Merged
Merged
Conversation
Laravel 11 reached end of security support and all 11.x releases are now flagged by security advisories with no patched version available, so Composer refuses to install them and the 11.* CI matrix cells fail. - Remove 11.* from the test matrix - Drop testbench ^9.0 and phpunit ^9.0/^10.0 (L11-era toolchain) - Update README requirements to Laravel 12-13
Raise minimum versions to current releases while keeping the wide multi-major test ranges: - jaybizzle/crawler-detect ^1.2 -> ^1.4 - matomo/device-detector ^6.0 -> ^6.5 - phpstan/phpstan ^2.1 -> ^2.2
|
coverage: 100.0%. remained the same — chore/drop-laravel-11 into main |
pataar
enabled auto-merge (squash)
June 19, 2026 11:08
pataar
disabled auto-merge
June 19, 2026 12:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Laravel 11 reached end of security support. Every released
11.*version (v11.0.0…v11.54.0) is now flagged by security advisories with no patched 11.x release available, so Composer (advisory blocking is on by default) refuses to install them. This breaks the11.*cells of the test matrix:The
12.*and13.*cells are unaffected.Changes
11.*from the test matrix (tests.yml)orchestra/testbench ^9.0andphpunit ^9.0 || ^10.0(the Laravel-11-era toolchain)Notes
The package remains installable on Laravel 11 —
composer.jsonnever pinnedlaravel/framework. We simply no longer test against an EOL, unpatchable framework.Verification
composer test→ 81 tests, 204 assertions, OKcomposer analyse→ no errorscomposer update→ resolves with no security advisories