Product Decisions This Supports

Framework and runtime roadmap: v3.1.0 adds Laravel 12 compatibility and fixes a PHP 8.4 implicit nullable deprecation. This supports keeping the package in the Laravel 12 / PHP 8.4 upgrade path instead of replacing it or building custom sender glue.
Build vs. buy: Use the maintained Saloon Laravel HTTP Sender as the integration layer between Saloon and Laravel’s HTTP client, reducing bespoke code and long-term compatibility risk.
API integration delivery: For Laravel applications using Saloon, this package supports third-party API integrations while preserving Laravel-native HTTP conventions such as testing/faking and middleware where applicable.
Release management: v3.1.0 is a compatibility/maintenance release with no breaking changes noted. PM action is to approve routine dependency updates and validate through CI rather than plan a migration project.

When to Consider This Package

Consider it when the product is a Laravel application using Saloon for outbound HTTP/API integrations and you want an official, maintained Laravel HTTP sender.
Consider it when you are planning or validating Laravel 12 and PHP 8.4 upgrades and want to reduce dependency compatibility risk.
Consider it when you value testable, framework-aligned HTTP integration over custom Saloon-to-Laravel transport code.
Look elsewhere if the application does not use Saloon or Laravel, if you need a non-Laravel transport, if package version constraints block your framework/runtime, or if you already have a stable custom integration and no upgrade pressure.

For executives: This is a low-risk maintenance update that keeps an API integration dependency compatible with current Laravel/PHP upgrades and avoids investment in bespoke glue code.
For engineering: v3.1.0 is a compatibility release: Laravel 12 support plus a PHP 8.4 deprecation fix, with no breaking changes called out. Update the dependency, run the existing test suite/CI, and continue using the package as the Saloon-to-Laravel HTTP sender.