Support Laravel 12/13 and Filament v5
- Dominant language
- PHP
- Stars
- 2
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
`composer.json` currently pins:
- `laravel/framework`: `^11.0`
- `filament/filament`: `^4.0`
This blocks installing the plugin in any AureusERP fork already upgraded to Laravel 13 /
Filament 5 — `composer require aureuserp/mcp` fails dependency resolution outright, since
`^11.0` and `^13.0` don't overlap:
Problem 1
- Root composer.json requires aureuserp/mcp ^1.0.3 -> satisfiable by aureuserp/mcp[v1.0.3].
- aureuserp/mcp v1.0.3 requires laravel/framework ^11.0 -> found laravel/framework[v11.0.0, ..., v11.56.0]
but it conflicts with your root composer.json require (^13.0).
A quick scan of `src/` didn't turn up any Filament v3/v4-only APIs (`Filament\Tables\Actions\*`,
`BadgeColumn`, etc.), so this may just be an untested/conservative constraint rather than an actual
code incompatibility — but that's unverified. Would upstream be open to widening the constraint to
`laravel/framework: ^11.0|^12.0|^13.0` and `filament/filament: ^4.0|^5.0` (or a dedicated v5
branch/tag), or is there a known blocker on the Filament v5 side?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with composer.json and inspect the Laravel and Filament constraints alongside the compatibility-sensitive code under src/. Run Composer dependency checks against Laravel 12/13 and Filament 5, then verify the package can install without resolution errors and that the existing test suite passes for the widened support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100