Slack Laravel Package

Getting Started

• Confirm your runtime first: this release is a framework-alignment major, so expect PHP 8.1+ and Laravel 10. Laravel 9 applications should stay on the 2.x line unless they upgrade the framework.
• Look first at composer.json (illuminate/support, illuminate/contracts, and related constraints should be ^10.0), then CHANGELOG.md / UPGRADE.md, the service provider, and any publishable config.
• Install into a Laravel 10 app with composer require vendor/package:^3.0. When upgrading an existing app, use composer require vendor/package:^3.0 --with-all-dependencies so Composer can re-resolve the framework graph.
• First use case: install in a fresh Laravel 10 skeleton, publish config/migrations if the package provides them, exercise the package’s primary entry point (route, command, job, or facade call), and confirm discovery with php artisan about or php artisan package:discover.
• After upgrading, run php artisan config:clear && php artisan cache:clear before judging whether the package works.

Implementation Patterns

• Pin ^3.0 in application composer.json for Laravel 10 projects. Keep a 2.x branch or constraint for Laravel 9 maintenance if you support both.
• Upgrade workflow: create a branch, bump the package constraint, run composer update vendor/package --with-all-dependencies, run the application test suite, smoke-test the package’s main integration points, then deploy.
• CI matrix: test against PHP 8.1, 8.2, and 8.3 with Laravel 10. For package development, use orchestra/testbench:^8.0 for Laravel 10 and keep older Testbench versions on older branches.
• Use Composer diagnostics before changing code: composer why-not vendor/package 3.0 and composer prohibits vendor/package 3.0 quickly identify packages still pinned to Laravel 9.
• Day-to-day integration: rely on Laravel package auto-discovery where possible. If the package requires manual registration, verify provider and facade aliases after the major bump—major versions sometimes rename or remove them.
• For package authors, add illuminate/support:^10.0 to require and orchestra/testbench:^8.0 to require-dev; keep test fixtures compatible with Laravel 10’s defaults.
• Prefer configuration publishing and container bindings over subclassing package internals. Bind contracts in a service provider and drive package behavior through published config and environment variables.

Gotchas and Tips

• A one-line changelog does not mean a low-risk release. 3.0.0 is a breaking major: it drops Laravel versions below 10 and PHP versions below 8.1. Do not auto-merge it in production without testing.
• Composer resolution is the most common blocker. Other dependencies pinned to Laravel 9 will prevent 3.0.0 from installing; upgrade the dependency graph, not just this package.
• --with-all-dependencies is frequently required when bumping a framework-aligned major. Without it, Composer may hold back the package or the framework.
• Clear cached artifacts after upgrading: config:clear, route:clear, view:clear, and queue:restart. Stale config and route caches can make a working package appear broken.
• Review Laravel 10 removals and deprecations that affect the package’s service provider, model casts, mail/queue integrations, and any doctrine/dbal-dependent column changes.
• If the package publishes migrations or config, re-publish or diff the published files after the major upgrade. Do not blindly overwrite application-specific customizations.
• For package maintainers, mismatched orchestra/testbench and Laravel majors is a common source of false test failures; keep Testbench aligned with the Laravel version under test.
• Debug with composer show vendor/package, composer prohibits, php artisan package:discover, and bootstrap/cache/packages.php to confirm the installed version and discovery state.
• Keep the constraint at ^3.0; avoid dev-main in production just to obtain Laravel 10 support. Major-version tags are the supported upgrade path.