|
2 | 2 |
|
3 | 3 | All notable changes to `filament-logger` will be documented in this file. |
4 | 4 |
|
| 5 | +## v0.9.0 - 2026-03-12 |
| 6 | + |
| 7 | +This release expands Filament Logger’s audit coverage, hardens default security behavior, improves the activity UI, and refreshes the package documentation. |
| 8 | + |
| 9 | +### Highlights |
| 10 | + |
| 11 | +- Added retention and pruning support with a new `filament-logger:prune` command. |
| 12 | +- Expanded auth logging to cover login, logout, failed login, lockout, password reset, and Fortify recovery-code usage when available. |
| 13 | +- Added ignored-field controls globally, per model, and per resource to reduce noisy or sensitive change logs. |
| 14 | +- Improved model lifecycle logging for restore, force-delete, replicate, and bulk-action flows. |
| 15 | +- Upgraded the activity detail view with a clearer side-by-side diff, pretty-printed JSON values, and collapsing for large payloads. |
| 16 | +- Hardened logging defaults to better protect sensitive data and reduce accidental exposure. |
| 17 | +- Rewrote the README and removed the temporary banner while a new one is being prepared. |
| 18 | + |
| 19 | +### Security Improvements |
| 20 | + |
| 21 | +- Activity resource access is now strict by default and requires explicit policy support. |
| 22 | +- Sensitive values such as passwords, tokens, secrets, and recovery codes are sanitized before being stored or displayed. |
| 23 | +- Access logs now anonymize IP addresses and limit stored user-agent size. |
| 24 | +- Notification recipient logging is disabled by default, with optional masking when enabled. |
| 25 | +- Existing historical records are not automatically rewritten, so older stored descriptions may still contain unsanitized values until scrubbed separately. |
| 26 | + |
| 27 | +### Audit Logging Improvements |
| 28 | + |
| 29 | +- Added structured old/new attribute logging for updates. |
| 30 | +- Added support for restore and force-delete lifecycle events without duplicate noise. |
| 31 | +- Added replicate logging with source metadata. |
| 32 | +- Added broader support for Filament bulk operations through lifecycle event handling. |
| 33 | +- Added per-model and per-resource ignore lists for fields like `updated_at`, counters, and session-related values. |
| 34 | + |
| 35 | +### UI Improvements |
| 36 | + |
| 37 | +- Added a richer activity diff viewer in the resource detail page. |
| 38 | +- Large payloads are now collapsible for easier inspection. |
| 39 | +- JSON-like values are formatted for readability. |
| 40 | + |
| 41 | +### Developer Experience |
| 42 | + |
| 43 | +- Added pruning configuration options by age and log name. |
| 44 | +- Improved test coverage for authorization, auth events, model lifecycle logging, pruning, and sanitization. |
| 45 | +- Fixed lifecycle snapshot handling so old values are captured reliably across supported Laravel versions. |
| 46 | +- Fixed resource observer registration so per-resource logger configuration is preserved correctly. |
| 47 | +- Filtered noisy PHP 8.4 PDO deprecation output during tests. |
| 48 | + |
| 49 | +### Documentation |
| 50 | + |
| 51 | +- README was overhauled to reflect the new logging, pruning, security, and configuration options. |
| 52 | +- The temporary README banner has been removed until it is redesigned. |
| 53 | + |
| 54 | +### Upgrade Notes |
| 55 | + |
| 56 | +- Add the `filament-logger:prune` command to your application scheduler if you want automatic cleanup. |
| 57 | +- If you rely on viewing the activity resource, make sure an `Activity` policy is registered or disable strict authorization explicitly. |
| 58 | +- Review the new config defaults for notification recipient logging and auth-event coverage. |
| 59 | +- Historical activity entries are not retroactively sanitized. |
| 60 | + |
5 | 61 | ## v0.8.2 - 2026-03-02 |
6 | 62 |
|
7 | 63 | **Full Changelog**: https://github.com/MrAdder/filament-logger/compare/v0.8.1...v0.8.2 |
|
0 commit comments