Added Laravel 13 support

[rfpdl]

Laravel 13 requires symfony/console: ^7.4 || ^8.0, and a stock Laravel 13 app on PHP 8.4+ resolves Symfony 8.1. Lucid caps Symfony at ^7.0, so it cannot be installed alongside it:

$ composer require lucidarch/lucid
  lucidarch/lucid dev-main requires symfony/console ^5.4|^6.0|^7.0 -> found
  symfony/console[...v7.4.17] but the package is fixed to v8.1.5 (lock file
  version) by a partial update

Adding -W makes it "work" by downgrading the host application's symfony/console, symfony/process and symfony/finder from 8.1.5 back to 7.4.17.

Widening the constraint alone isn't enough

Lucid also fatals on Symfony 8, which made two breaking changes it relies on:

• Command::configure() gained a : void return type
• Application::add() was removed in favour of addCommand()

Both are new in Symfony 8 — 6.4 and 7.4 are unaffected, so this isn't a latent bug surfacing.

PHP Fatal error: Declaration of Lucid\Console\Commands\FeatureMakeCommand::configure()
must be compatible with Symfony\Component\Console\Command\Command::configure(): void

The change

Three lines, plus CI and docs:

1. composer.json — the four symfony/* constraints go from ^5.4|^6.0|^7.0 to ^5.4|^6.0|^7.0|^8.0
2. src/Console/Command.php — configure() becomes configure(): void
3. lucid — array_walk($commands, [$app, 'add']) becomes $app->addCommands($commands)

addCommands() exists in every supported Symfony major (5.4 through 8.1) and delegates to addCommand() on 8.x, so no version branching is needed. Adding the : void return type is a legal narrowing on 5.4/6.4/7.4, where the parent declares none.

Commits are ordered so the code support lands before the constraint — otherwise there's a commit where Symfony 8 is installable but unsupported.

php stays at ^8.1

Symfony 8 requires PHP >= 8.4.1, so PHP 8.1 through 8.3 hosts resolve Symfony 7.4 or lower on their own. Requiring ^8.0 alone would break Laravel 13 users on PHP 8.3 and drop Laravel 9 through 12 entirely. Laravel itself accepts ^7.4 || ^8.0 for the same reason.

Verification

Installed and ran bin/test-commands.sh against real apps:

• Laravel 13.29.0 on PHP 8.4 resolves Symfony 8.1.6 — passes
• Laravel 13.29.0 on PHP 8.3 resolves Symfony 7.4.18 — passes
• Laravel 12 on PHP 8.5 resolves Symfony 7.4.17 — passes
• Laravel 9.21.0 on PHP 8.1 with --prefer-lowest resolves Symfony 6.0.2 — passes

composer require lucidarch/lucid into a stock Laravel 13 app now succeeds without -W, and composer show symfony/console still reports v8.x afterwards, so the host is no longer downgraded.

CI

Adds a 13.x axis, excluding PHP 8.1 and 8.2 which Laravel 13 doesn't support.

Two include: cells pin the resolved Symfony major (PHP 8.3 to 7, PHP 8.4 to 8) so a future resolution change can't silently drop one of the two paths this PR supports.

The Lucid require step deliberately has no -W: if the constraint is ever too narrow for the host's Symfony, that step should fail loudly rather than quietly downgrade the host, which is the bug being fixed here.

No new public concepts, no version branches, and backwards compatible with Laravel 9 through 12.

🤖 Generated with Claude Code