What changed
On 10 November 2026 Laravel News documented Lomkit's Laravel REST API 3 rewrite. The upstream upgrade guide confirms typed field/input declarations, a common request validation and authorisation perimeter, Scramble OpenAPI documentation, metrics endpoints and signed confirmations for sensitive operations. The 3.x series has already received further releases, so teams must consult the upgrade guide for their target version.
Why it matters
A package that generates CRUD APIs from Eloquent resource classes sits at an application's authorisation boundary. This migration changes how fields, queries and writes are validated and exposed. Upgrading blindly can break client contracts or policy behaviour. Small Laravel teams need a compatibility inventory, controlled staging upgrade and targeted API regression tests.
The resource contract has changed
In 2.x resource declarations could list column names; 3.x uses typed field objects that drive input validation, filters, response serialization and documentation. Query hooks consolidate into perimeterQuery(), and declarations no longer receive the old request argument. Overrides retaining old signatures can fail at PHP class loading.
Compatibility is a hard gate
The official 3.0 upgrade guide requires PHP 8.3+ and Laravel 13.30+. Laravel 12 applications should remain on the 2.x line until the framework is upgraded. Laravel Scout integrations require version 11.9+, while Scramble ^0.13.48 is used for OpenAPI documentation.
Safer writes require client awareness
The package introduces signed confirmation tokens and HTTP 428 responses for operations requiring confirmation. Clients must handle that handshake rather than assume all write requests either succeed or return conventional validation errors. Later 3.x changes also adjust 422 and 409 behaviour for specific invalid relation operations.
Migration needs testing, not only documentation
The maintainer's guide recommends updating resource classes, running php artisan rest:check, checking php artisan route:list and exercising tests after each step. Verify authorisation boundaries, relationship mutations, filters, pagination, response shape and generated OpenAPI against real clients. The documentation establishes intended behaviour, not proof that an individual application will migrate without regressions.