2.3.1
October 27th, 2026
Documentation only. No code changed between v2.3.0 and v2.3.1, so there is nothing to do beyond composer update whenever it suits you. If you are coming from 2.2.x or earlier, the notes that matter are in v2.3.0.
Changed
The README reads in the order you need it
It used to open with roughly 150 lines of feature tour and widget screenshots before mentioning how to install anything — and "Required: database credentials" sat about 100 lines below the install commands, so the one prerequisite for php artisan logbook:install came after the step that needs it. Upgrade notes were the first thing under Setup, which a first-time reader met before any install instructions.
The order is now:
Quick start → Compatibility → Installation → Setup → Check it is working → Configuration
with the feature tour and the advanced material (ingestion modes, spool scheduling, operational commands) behind it, and upgrade notes at the end of Setup.
A four-step quick start
Copy-pasteable, ending in a table that points at the right section for whatever you want next. The zero-config path is now stated accurately: the Control Panel setup screen prefills from your application's own database connection when no LOGBOOK_DB_* is set, so Connect & install really is the whole setup.
Fixed
- Compatibility claimed Laravel 9–12. Laravel 13 has been supported since 2.0.2 and is now listed.
- Undocumented command flags:
logbook:prune --days=, andlogbook:flush-spool --type/--limit/--dry-run. Logfacade calls in examples are fully qualified, so they work pasted into a namespaced file rather than only at the root namespace.- Test Coverage listed neither the suite size nor the four test classes added in 2.3.0.
Added
"Which log channel a row belongs to"
v2.3.0 made channel names real, but ignore_channels is only usable if you know what it matches on. The new section shows the names Laravel reports for each kind of write:
#292D3E; --theme-selection-background: #00000080;">#89DDFF;">\Log#89DDFF;">::#82AAFF;">info#89DDFF;">(#89DDFF;">'to the default channel#89DDFF;">'#89DDFF;">); #676E95;">// channel: stack#89DDFF;">\Log#89DDFF;">::#82AAFF;">channel#89DDFF;">(#89DDFF;">'single#89DDFF;">'#89DDFF;">)->#82AAFF;">warning#89DDFF;">(#89DDFF;">'to one file#89DDFF;">'#89DDFF;">); #676E95;">// channel: single#89DDFF;">\Log#89DDFF;">::#82AAFF;">channel#89DDFF;">(#89DDFF;">'slack#89DDFF;">'#89DDFF;">)->#82AAFF;">error#89DDFF;">(#89DDFF;">'to Slack#89DDFF;">'#89DDFF;">); #676E95;">// channel: slack
…along with the deprecations default that now genuinely drops rows, and the Log::build() / Log::stack() limitation.
Env var coverage was cross-checked against config/logbook.php in both directions: 29 documented, 29 read — no omissions, and nothing documented that the config never reads.
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/compare/v2.3.0...v2.3.1
2.3.0
October 27th, 2026
Two user-reported fixes: #3 and #4.
No schema change and nothing to run. composer update is the whole upgrade.
#292D3E; --theme-selection-background: #00000080;">composer require emran-alhaddad/statamic-logbook:^2.3
Fixed
System logs record the channel they actually came from (#3)
Every system-log row used to be stored with the channel logbook, and logbook.system_logs.ignore_channels matched nothing — the capture listener read $event->channel, and Illuminate\Log\Events\MessageLogged has no such property (it carries only level, message and context). Monolog's own $record->channel is no substitute either: Laravel names every Monolog logger $config['name'] ?? app.env, so a channel without an explicit name reports production.
Logbook now attaches a lazy Laravel log tap to each channel in config/logging.php, which labels that channel's records with its real name on the way through. A stack channel reports stack rather than one of its sub-channels, and the marker is stripped from the Monolog record before any handler runs, so nothing new appears in your own laravel.log.
The deprecations channel is covered too. Laravel only materialises its config the first time a deprecation fires — after addon boot — so Logbook seeds it the way the framework does, and the shipped ignore_channels => ['deprecations'] default finally drops deprecation rows as documented, NullHandler or not.
Channels the host registers after boot, and on-demand loggers from Log::build() / Log::stack(), carry no name Laravel can report; their records are still captured, under the logbook fallback.
vendor:publish --tag=logbook publishes something (#4)
The README has always documented that tag, but Statamic registers addon assets under the addon slug (statamic-logbook) and skips its own bootConfig() for a config file that is not named after the slug — so the documented command reported "No publishable resources for tag [logbook]". Three tags are now registered:
| Tag | Publishes |
|---|---|
logbook |
config + CP stylesheet + CP script |
logbook-assets |
CP stylesheet + CP script only (safe to --force) |
logbook-config |
config/logbook.php only |
The config stays out of the statamic-logbook tag on purpose: Statamic force-publishes that tag after statamic:install, which would overwrite an edited config/logbook.php on every composer update.
Added
CP assets publish themselves (#4)
Statamic only force-publishes addon assets from statamic:install, which plenty of deploys never run, and a composer update that ships a newer bundle leaves the old published copy in place — both of which surface as an unstyled Control Panel. Logbook now copies anything missing or stale into public/vendor/statamic-logbook/ on the first CP request of each process, then no-ops. It fails soft and silently on a read-only public/, and php artisan logbook:install publishes the bundles as well.
LOGBOOK_ASSETS_AUTO_PUBLISH=false (logbook.assets.auto_publish) turns the runtime copy off for immutable deploys — publish during the build instead:
#292D3E; --theme-selection-background: #00000080;">php artisan vendor:publish --tag=logbook-assets --force
One behaviour change worth knowing about
If your app routes PHP deprecations through Log::channel('deprecations'), those rows stop being recorded, because ignore_channels now works and deprecations is in the shipped default. That was always the documented intent. To keep recording them:
#292D3E; --theme-selection-background: #00000080;">LOGBOOK_SYSTEM_LOGS_IGNORE_CHANNELS#89DDFF;">=
Existing rows are untouched and keep their logbook channel. See UPGRADE.md for the full upgrade note, and CHANGELOG.md for the detail.
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/compare/v2.2.0...v2.3.0
2.2.0
July 29th, 2026
- N/A Changelog not available.
2.1.0
July 29th, 2026
- N/A Changelog not available.
2.0.2
April 27th, 2026
- N/A Changelog not available.
2.0.1
April 23rd, 2026
- N/A Changelog not available.
2.0.0
April 22nd, 2026
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/compare/v1.5.2...v2.0.0
1.5.2
April 16th, 2026
- N/A Changelog not available.
1.5.1
April 15th, 2026
- N/A Changelog not available.
1.5.0
April 15th, 2026
- N/A Changelog not available.
1.4.0
April 15th, 2026
- N/A Changelog not available.
1.3.2
April 16th, 2026
What's Changed
- Clean widgets by @emran-alhaddad in https://github.com/emran-alhaddad/statamic-logbook/pull/1
- fix: add v-pre directive to logbook layout and pulse widget by @emran-alhaddad in https://github.com/emran-alhaddad/statamic-logbook/pull/2
New Contributors
- @emran-alhaddad made their first contribution in https://github.com/emran-alhaddad/statamic-logbook/pull/1
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/compare/v1.5.1...1.3.2
1.3.1
April 14th, 2026
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/compare/v1.3.0...v1.3.1
1.3.0
April 13th, 2026
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/compare/v1.2.0...v1.3.0
1.2.0
April 13th, 2026
- N/A Changelog not available.
1.1.0
April 8th, 2026
- N/A Changelog not available.
1.0.0
December 13th, 2025
Full Changelog: https://github.com/emran-alhaddad/statamic-logbook/commits/v1.0.0