Sms Laravel Package

Getting Started

• Treat 10.0.0 as a platform-support and tooling release, not a feature release. The main day-to-day impact is the new support matrix: PHP 8.4/8.5 and Laravel 11/12/13.
• Before installing, confirm your app is already on:
  • PHP >=8.4
  • Laravel >=11
• Start with composer.json and the package README/upgrade guide. The release notes explicitly mention docs fixes, so read the current docs rather than relying on older examples.
• First use case: install the package in a Laravel 12 app running PHP 8.4, publish any package config/assets if applicable, and run the package’s smoke test or a minimal feature path.
• If upgrading from 9.x, upgrade PHP and Laravel first, then update the package. Do not try to jump both the framework and package constraints at once without a clean platform baseline.

Implementation Patterns

• Pin to the new support matrix in CI. Use a matrix such as PHP 8.4/8.5 × Laravel 11/12/13 so day-to-day changes do not accidentally rely on dropped versions.
• Use Composer platform checks as the first gate. Run composer why-not package/name 10.0.0 when an upgrade is blocked; it quickly shows whether PHP or Laravel constraints are the issue.
• Upgrade workflow:
  1. Update PHP to 8.4+.
  2. Update Laravel to 11+.
  3. Require the package at ^10.0.
  4. Run the app’s test suite and static analysis.
  5. Only then address package-specific API changes, if any.
• Contributor/maintainer workflow: tests are now Pest-based. Use pest/composer test as documented rather than assuming PHPUnit commands. Static analysis is now PHPStan/LaraStan, so use the package’s LaraStan config and CI commands instead of Psalm.
• Integration tip: because Laravel 13 compatibility is called out, verify Laravel 13 apps separately if you maintain multiple Laravel versions. Laravel 13 may require stability flags depending on the release state of your dependency tree.
• Keep package usage behind your own service/provider boundaries where possible. That makes future major-version support-matrix changes cheaper to absorb.

Gotchas and Tips

• Hard breaking changes: PHP <8.4 and Laravel <11 are no longer supported. Composer will block installation on older platforms; this is expected, nota package bug.
• Laravel 13 compatibility does not mean Laravel 10 still works. The release explicitly removes Laravel support older than 11.
• Pest migration changes test commands and conventions. If you contribute to or extend the package, do not assume PHPUnit-style test invocation or class structure.
• PHPStan/LaraStan replaces Psalm. Old Psalm configs, baseline files, and CI steps are stale. Use the package’s LaraStan setup and update your own static-analysis pipeline if you copy its patterns.
• Docs were fixed, but old examples may still circulate. Check the current README and upgrade notes before copying older snippets from blog posts or previous versions.
• Debugging upgrade failures: run composer diagnose, composer why-not, and php -v first. Most 10.0.0 install failures will be platform constraints rather than runtime errors.
• Extension points are unchanged by this release. Continue using the package’s documented service provider, config publishing, and container bindings as before; 10.0.0 does not advertise new runtime APIs.
• If your app must stay on PHP 8.3 or Laravel 10, stay on the previous major line and plan the platform upgrade separately.