Getting Started

Install on PHP 7.4+ with composer require shimabox/laqu:^0.4. v0.4.0 drops PHP 7.3 support, so PHP 7.3 projects must stay on v0.3.2 or upgrade PHP first.
Look first at the package README/CHANGELOG and its composer.json PHP constraint, then confirm your app/CI platform matches.
First use case: upgrade an existing v0.3.x integration on a PHP 7.4+ Laravel app and run the existing test suite. v0.4.0 is a compatibility/maintenance release; there are no new API features called out to learn.

Implementation Patterns

Treat v0.4.0 as a drop-in runtime-floor bump: existing package usage/configuration from v0.3.x should continue unchanged on supported PHP versions.
Pin the package in composer.json with "shimabox/laqu": "^0.4" and update CI matrices to PHP 7.4+ before merging.
For shared libraries or legacy apps still targeting PHP 7.3, keep a ^0.3 constraint or add a platform/package constraint that prevents accidental v0.4 installation.
Keep existing controller/service-layer usage as-is; this release does not introduce new workflows or extension points to adopt.

PHP 7.3 is now a hard upgrade blocker. Check composer.json, config.platform.php, Docker images, and CI runners before upgrading.
Composer may fail on transitive dependencies after the bump even if the package itself is fine. Use composer why-not shimabox/laqu 0.4.0 and composer check-platform-reqs to diagnose.
If you maintain a downstream package, declare your PHP requirement clearly so consumers do not resolve v0.4 on PHP 7.3.
Debug upgrade issues with composer update shimabox/laqu --with-dependencies in a clean environment; avoid rewriting application code for this release since the change is only the PHP support floor.