Add Laravel 13 support to illuminate dependency constraints#6
Conversation
Widens `illuminate/support` and `illuminate/contracts` constraints to include `^13.0` alongside the existing `^11.0|^12.0` ranges. No source code changes are required: the package uses only the public surface of `Illuminate\\Support\\ServiceProvider`, `Illuminate\\Contracts\\Foundation\\Application`, and `Illuminate\\Support\\Facades\\Facade`, none of which broke between Laravel 11 → 12 → 13. Tested by installing this branch into a Laravel 13.8.0 project (with filament/filament v5.6.2, livewire/livewire v4.3.0, pestphp/pest v4.7.0) and verifying: - composer validate --strict exits 0 - composer update --with-dependencies resolves cleanly - php artisan about boots without fatals on Laravel 13.8.0 - ForerunnerServiceProvider auto-discovery works (Schema facade registered) Without this widening, installing forerunner v0.2.1 into a Laravel 13 project fails with: blaspsoft/forerunner v0.2.1 requires illuminate/contracts ^11.0|^12.0 Only one of these can be installed: laravel/framework[v13.0.0 ...], illuminate/contracts[v11.0.0 ... v12.x]. laravel/framework replaces illuminate/contracts and thus cannot coexist with it.
📝 WalkthroughWalkthroughThe PR updates two Laravel framework dependency constraints in ChangesDependency Version Expansion
🎯 1 (Trivial) | ⏱️ ~2 minutes
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
composer.json (1)
17-23:⚠️ Potential issue | 🟠 Major | ⚡ Quick winAdd
orchestra/testbench^11.0 to support Laravel 13 CI testing.The current constraint
^9.0|^10.0covers Laravel 11 and 12 only. To validate the Laravel 13 support claim in CI, include testbench v11.0.0+, which requires Laravel 13:Required update
- "orchestra/testbench": "^9.0|^10.0" + "orchestra/testbench": "^9.0|^10.0|^11.0"🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@composer.json` around lines 17 - 23, Update the composer dev dependency constraint for orchestra/testbench in require-dev so CI can test Laravel 13; replace the current constraint "orchestra/testbench": "^9.0|^10.0" with a range that includes v11 (for example "^9.0|^10.0|^11.0" or "^9.0|^10.0|^11.0|^12.0" as appropriate) in composer.json to allow installing testbench v11.x for Laravel 13 testing.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@composer.json`:
- Around line 17-23: Update the composer dev dependency constraint for
orchestra/testbench in require-dev so CI can test Laravel 13; replace the
current constraint "orchestra/testbench": "^9.0|^10.0" with a range that
includes v11 (for example "^9.0|^10.0|^11.0" or "^9.0|^10.0|^11.0|^12.0" as
appropriate) in composer.json to allow installing testbench v11.x for Laravel 13
testing.
1 participant
Summary
Widens
illuminate/supportandilluminate/contractsconstraints from^11.0|^12.0to^11.0|^12.0|^13.0so the package installs cleanly into Laravel 13 projects.What changes
No source changes — the package uses only the public surface of
Illuminate\Support\ServiceProvider,Illuminate\Contracts\Foundation\Application, andIlluminate\Support\Facades\Facade. None of these broke between Laravel 11 → 12 → 13.Why
Installing
blaspsoft/forerunner ^0.2.1into a Laravel 13 project currently fails resolution:Test plan
composer validate --strictexits 0filament/filament v5.6.2,livewire/livewire v4.3.0,pestphp/pest v4.7.0php artisan aboutboots without fatalsForerunnerServiceProviderauto-discovery works (Schema facade registered)^13.0to your test matrix if not present)Summary by CodeRabbit