Flarum Laravel Session Laravel Package

Getting Started

Treat 0.6.0 as a platform-baseline release: it adds Laravel 13 support and intentionally drops older PHP/Laravel versions. Before adopting it day-to-day, confirm your app is already on the new baseline:

• PHP >= 8.4
• Laravel >= 13
• Package constraint pinned to ^0.6

Minimal upgrade path:

php -v
composer show laravel/framework
composer require vendor/package:^0.6
php artisan package:discover
php artisan optimize:clear

Look first at the package’s composer.json, service provider registration, config publishing, and any UPGRADE/README notes. The first practical use case is unchanged package usage inside a Laravel 13 app: install 0.6.0, verify auto-discovery or manual provider registration, publish config/migrations if the package requires it, and smoke-test the primary workflow in staging.

Implementation Patterns

Use 0.6.0 as the minimum supported version in new Laravel 13 applications, and keep the constraint explicit rather than allowing older versions to resolve accidentally:

{
  "require": {
    "php": "^8.4",
    "laravel/framework": "^13.0",
    "vendor/package": "^0.6"
  }
}

Day-to-day patterns:

• Rely on Laravel package discovery where available; if the package registers manually, add the provider in bootstrap/providers.php.
• Resolve package services through the container and inject dependencies rather than using static calls.
• Keep published config in config/ and environment-specific values in .env; avoid editing vendor files.
• Wrap package calls behind a small application service or adapter if the package is central to your domain, so future upgrades stay contained.
• In CI, test only the supported matrix for this branch: PHP 8.4 and Laravel 13. Add a separate legacy job only if you still maintain a 0.5.x branch.
• For upgrades, create a branch, update Composer constraints, run the full test suite, clear caches, and restart queue workers.

Because the release notes list only compatibility changes, existing 0.5.x usage patterns should generally carry forward—but only on Laravel 13/PHP 8.4.

Gotchas and Tips

• Breaking baseline: PHP < 8.4 and Laravel < 13 are no longer supported. Do not install 0.6.0 in legacy apps; stay on 0.5.x there.
• Composer may not fail loudly enough if your constraints allow older package versions. Pin ^0.6 and verify with composer show vendor/package.
• If resolution fails, use composer why-not vendor/package 0.6.0 to find the blocking PHP, Laravel, or transitive dependency constraint.
• Check transitive dependencies for Laravel 13/PHP 8.4 compatibility, not just the package itself.
• After upgrading, clear cached package discovery and config: php artisan optimize:clear, and restart long-running workers.
• Run tests with strict error reporting to catch PHP 8.4 deprecations early.
• Since 0.6.0 appears compatibility-focused, do not expect new feature APIs. Focus regression testing on the package’s existing primary workflow and integration points.
• Use the package’s config, events, and contracts as extension points where documented, but verify them against the 0.6.0 README/UPGRADE notes before relying on them.