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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,14 @@ All notable changes to `filament-activity-log` will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [1.1.3] - 2025-12-15
9
+
10
+
### Fixed
11
+
12
+
-**Custom Authorization Serialization** - Fixed `Your configuration files could not be serialized` error when using `custom_authorization` with config caching.
13
+
- Added support for Class-Based Authorization (`checkCustomAuthorization` in `ActivityPolicy`).
14
+
- Updated documentation with examples and troubleshooting steps.
-`custom_authorization` takes **precedence** over the `enabled` setting
@@ -304,6 +332,16 @@ And assign them through Filament Shield's UI.
304
332
},
305
333
```
306
334
335
+
### Issue: Configuration serialization error
336
+
337
+
**Error:**`Your configuration files could not be serialized because the value at "filament-activity-log.permissions.custom_authorization" is non-serializable`
338
+
339
+
**Solution:**
340
+
341
+
You are likely running `php artisan config:cache` while using a Closure in your config file. Closures cannot be serialized.
342
+
343
+
To fix this, switch to **Class-Based Authorization** (see Example 5 above) or remove the config cache if not needed (`php artisan config:clear`).
0 commit comments