# Version 3: the exception tracker, 2023 to 2026

Published on 14 March 2023 at https://www.larabug.com/changelog/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 one `LB_DSN` value 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:scan` command 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

- The package, PHP and Laravel versions sent with every report (Added, SDK, larabug/larabug 3.8.4)
- A crash at boot on Laravel 6.0 to 6.9 (Fixed, SDK, larabug/larabug 3.8.3)
- The JavaScript report route no longer reads a file named by the caller, and is throttled (Security, SDK, larabug/larabug 3.8.2)
- Exceptions grouped by a fingerprint instead of by their raw message (Improved, Panel)
- CVE scanning of the Composer lockfile, and larabug:scan to run one on demand (Added, SDK, larabug/larabug 3.8.0)
- Your time zone and a default time span, as preferences (Added, Panel)
- Laravel 13 support (Added, SDK, larabug/larabug 3.6.1)
- A default for the environments setting when the published config has none (Fixed, SDK, larabug/larabug 3.5.2)
- A badge on a JavaScript error for the framework it came from (Added, Panel)
- Delivery that batches itself against load (Improved, SDK, larabug/larabug 3.5.1)
- Queue and job reporting (Added, SDK, larabug/larabug 3.5.0)
- Select all on the exceptions and issues tables (Added, Panel)
- Custom context data on an exception, with LaraBug::context() (Added, SDK, larabug/larabug 3.4.0)
- One DSN for the whole configuration, in LB_DSN (Added, SDK, larabug/larabug 3.4.0)
- [Database cache keys longer than 255 characters](https://github.com/LaraBug/LaraBug/issues/103) (Fixed, SDK, larabug/larabug 3.3.1)
- Laravel 12 support (Added, SDK, larabug/larabug 3.3)
- A webhook that keeps failing is switched off (Improved, Panel)
- PHP 8.2, 8.3 and 8.4 support (Added, SDK, larabug/larabug 3.2)
- Laravel 11 support (Added, SDK, larabug/larabug 3.1)
- Laravel 10 support (Added, SDK, larabug/larabug 3.0)
