Getting Started

Install/update with composer require <vendor>/<package>:^6.0.1 and confirm composer.json allows Laravel 9 (illuminate/* ^9.0) and PHP 8.0+.
Look first at the package README, UPGRADE.md if present, the service provider, and any publishable config/migrations.
First use case: upgrade a Laravel 8 app to Laravel 9, update this package to 6.0.1, clear caches, and smoke-test the package’s primary feature with a small feature test.
Run php artisan vendor:publish --provider="..." only if the package exposes config/assets/migrations, then run migrations in a non-production environment first.

Implementation Patterns

Rely on Laravel package discovery where possible; register the provider manually only if the package docs require it.
Resolve package services via dependency injection or the documented facade/helper, and keep package calls behind small application services where practical.
Publish package config into config/ and drive environment-specific values through .env; validate with php artisan config:cache in deployment.
In tests, use Laravel 9’s test helpers, RefreshDatabase when the package touches the DB, and assert the package’s public behavior rather than internals.
For the Laravel 9 upgrade, pin 6.0.1, run the full test suite, and compare behavior against the previous Laravel version before rolling out.

Laravel 9 requires PHP 8.0+; update CI and local tooling before debugging package behavior.
The release note only calls out Laravel 9 support—do not assume Laravel 10+ compatibility or API changes beyond what the README/changelog documents.
Clear config, route, view, and package-discovery caches after upgrading; stale caches often mimic package bugs.
Check Composer constraints with composer why-not <vendor>/<package> 6.0.1 if installation fails.
Review published migrations/config for Laravel 9-specific changes, especially if the package touches schema, queues, or broadcasting.
Use php artisan about, composer show, and package logs to debug integration issues; verify service-provider boot order if bindings are missing.
Prefer config and container bindings as extension points over editing vendor files; keep customizations in app-level providers.