You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Crash reports carry the journey to the failure: breadcrumbs from your logs, views, queries and queued jobs, plus dump()-style peeks and performance timings
Crashes are fingerprinted across occurrences, so editing unrelated code doesn't split one issue into many, and occurrence counts survive with an attached store
Sensitive values are redacted from reports before anything renders or ships
The debug crash page renders in Leaf's design language, and production gets a clean branded page that hides internals from users, never from you
Added Leaf\Crash\Pages: the framework's 404, maintenance, CSRF and generic error pages, rendered in the same design with dark mode support
Added Report::toText() for consoles and logs β Leaf MVC's command errors render through it
Custom error handlers plug in through renderWith(), receiving the full Report
Test suite runs through Alchemy
Changed
The whoops-based library is removed.Leaf\Exception\Run, its handlers, and Leaf\Exception\General are gone β Crash handles every error surface. If you called Leaf\Exception\General for status pages, Leaf\Crash\Pages has the same methods (default404, defaultDown, csrf, error)
Dropped the psr/log dependency β the package now has zero runtime dependencies
Exception now requires PHP 8.2+ and jumps from v3.7 to v5.0 to version alongside the rest of Leaf 5