v5.4.0

CoreKernel: a minimal kernel for leaner custom boots

The framework kernel is now split into two layers. A new public CoreKernel registers only the essentials — environment, response handler, storage path, and the router/middleware/loader capsules plus an empty command registry. The standard Kernel extends it to add the built-in craft commands and, only under the test runner, the test response capsule.

Subclass CoreKernel when you want a slimmer boot (a queue worker, an embedded service) that doesn't need the full command line.

Lighter imports

All command and testing imports inside the kernels are now lazy. Importing masonite.foundation no longer pulls in cleo, the command suite, or the testing helpers, and production boots never import the testing helpers at all.

Upgrading from 5.3

Drop-in upgrade — the standard Kernel behaves exactly as before. One behavior change: the tests.response capsule is now bound only when running under the test runner. If you relied on that binding outside of tests, register it in a service provider.

Full notes: https://docs.masonite.dev/whats-new/masonite-5.4/