Version 3: the exception tracker, 2023 to 2026
Version 3
Version three was LaraBug as an exception tracker: an application reports what it throws, the panel groups it into issues, and a mail or a webhook tells you. The 3.x line ran from March 2023 until version four replaced it in November 2026. This entry is what shipped in those years: by year here, and line by line underneath.
2023 and 2024
Package 3.0 came out on 14 March 2023 with Laravel 10 support, and 3.1 followed in June 2024 with Laravel 11. Little else changed in these two years.
2025
Package 3.2 added PHP 8.2, 8.3 and 8.4 in January, and 3.3 added Laravel 12 in March. In the panel, a webhook that kept failing was switched off instead of being called again on every exception.
2026
Most of what version three shipped came in its last year, while version four was being built beside it.
- January. Package 3.4 added custom context on an exception with
LaraBug::context(), and oneLB_DSNvalue in place of two keys. 3.5 added queue and job reporting, and 3.5.1 made it batch its own deliveries under load. In the panel, the exceptions and issues tables got a select all. - February and March. A JavaScript error got a badge for the framework it came from. Package 3.6 added Laravel 13.
- April. Your time zone and a default time span became preferences.
- July. Package 3.8 added CVE scanning of the Composer lockfile, on by default, and the
larabug:scancommand to run a scan on demand. - September. Package 3.8.2 was a security fix: the route the package registers for JavaScript reports read a file named by the caller, and no longer does. Anyone still on 3.x should be on 3.8.2 or later. In the panel, exceptions were grouped by a fingerprint instead of by their raw message, so one error with a changing message stopped opening an issue per message.
- November. 3.8.3 fixed a crash at boot on Laravel 6.0 to 6.9, and 3.8.4 sends the package, PHP and Laravel versions with every report.
Still on 3.x
An application on a 3.x package keeps reporting its exceptions to version four. The line has its own branch, and 3.8.4 is its latest release. Moving to 4.x is one command: composer require "larabug/larabug:^4.0" -W.
What changed
Every item this release closed: what kind of change it was, and the part of LaraBug it changed. A package line names the client and the version it shipped in.
- Added The package, PHP and Laravel versions sent with every report larabug/larabug 3.8.4 SDK
- Fixed A crash at boot on Laravel 6.0 to 6.9 larabug/larabug 3.8.3 SDK
- Security The JavaScript report route no longer reads a file named by the caller, and is throttled larabug/larabug 3.8.2 SDK
- Improved Exceptions grouped by a fingerprint instead of by their raw message Panel
- Added CVE scanning of the Composer lockfile, and larabug:scan to run one on demand larabug/larabug 3.8.0 SDK
- Added Your time zone and a default time span, as preferences Panel
- Added Laravel 13 support larabug/larabug 3.6.1 SDK
- Fixed A default for the environments setting when the published config has none larabug/larabug 3.5.2 SDK
- Added A badge on a JavaScript error for the framework it came from Panel
- Improved Delivery that batches itself against load larabug/larabug 3.5.1 SDK
- Added Queue and job reporting larabug/larabug 3.5.0 SDK
- Added Select all on the exceptions and issues tables Panel
- Added Custom context data on an exception, with LaraBug::context() larabug/larabug 3.4.0 SDK
- Added One DSN for the whole configuration, in LB_DSN larabug/larabug 3.4.0 SDK
- Fixed Database cache keys longer than 255 characters larabug/larabug 3.3.1 SDK
- Added Laravel 12 support larabug/larabug 3.3 SDK
- Improved A webhook that keeps failing is switched off Panel
- Added PHP 8.2, 8.3 and 8.4 support larabug/larabug 3.2 SDK
- Added Laravel 11 support larabug/larabug 3.1 SDK
- Added Laravel 10 support larabug/larabug 3.0 SDK
Missing something, or spotted a mistake? Say so on the roadmap. It is where the next entries on this page are decided.