Laravel Response Compression Laravel Package

Getting Started

This release is primarily a compatibility and hygiene release, so the first thing to establish is which Laravel line you are on.

1. Check your Laravel version. 3.3.0 adds Laravel 13 support and drops Laravel 11. If you are on Laravel 11, stay on the 3.2.x line — do not run composer update blind.
2. Constrain explicitly. In composer.json, require "vendor/package": "^3.3" and let the package's own illuminate/* constraint resolve. Avoid pinning laravel/framework to a version the package no longer advertises.
3. Confirm discovery. Run php artisan about and php artisan package:discover to verify the service provider is still auto-registered after the upgrade.
4. First use case: upgrade a single non-critical application, clear config/route/view caches, and exercise the package's main entry point (its facade, artisan command, or middleware) before touching anything else.

Implementation Patterns

Version-gated CI matrix. Test the package across the combinations you actually support rather than one job:

matrix:
  php: ['8.2', '8.3', '8.4']
  laravel: ['12.*', '13.*']

Since Laravel 11 is gone, remove those matrix legs — leaving them in produces misleading green/red signals.

Treat the PHPStan fixes as a reason to re-run analysis, not to relax it. 3.3.0 corrected typing errors, which means previously suppressed or baselined findings may now resolve differently. Regenerate your baseline after upgrading and review the diff; a shrinking baseline is a good sign, but silently dropping ignoreErrors entries can hide real regressions.

Separate the upgrade commit from feature work. Do the constraint bump, composer update, and test run as an isolated commit so a bisect later points at the right change.

Testing fixes mean your test dependency set may shift. If you extend the package's testing helpers or rely on its fixtures, re-run your suite with --order-by=random to surface state leakage the fixed tests may have masked.

Adopt early on Laravel 13 apps, cautiously elsewhere. For greenfield Laravel 13 projects, 3.3.0 is the minimum viable version. For existing Laravel 12 apps there is no functional gain — schedule the bump with your normal dependency cadence.

Gotchas and Tips

• Dropping Laravel 11 is a breaking change in practice, even though it ships as a minor. Composer will refuse the upgrade on an 11 app, but transitive resolution can still shift if another package pulls 3.3.0 in. Check composer why-not vendor/package 3.3.0 when you hit an unexpected conflict.
• Laravel 13 support may depend on a pre-release framework version. If composer update complains about stability, check whether you need "minimum-stability": "dev" with "prefer-stable": true — and remove it once 13 goes stable.
• Clear caches after upgrading. php artisan optimize:clear resolves the majority of "provider not found" and stale config reports following a version bump.
• Don't trust a green suite alone. The release notes mention fixed testing errors, which suggests the package's own suite was previously flaky or incomplete. Run the package's tests against your app's PHP version rather than assuming coverage.
• Debugging: when reporting an issue, include composer show vendor/package, php artisan --version, and PHP version. Type-related fixes mean the maintainers will likely ask for a PHPStan/Larastan output snippet.
• Extension points: if you have subclassed package classes or overridden typed methods, re-check signatures — tightened PHPStan types often accompany docblock/return-type corrections that can break inheritance on PHP 8.4.
• Pin for reproducibility in CI. Use composer update --prefer-lowest in at least one job to catch a too-narrow dependency declaration before your users do.