Skip to content

Releases: spatie/laravel-permission

2.36.1

05 Mar 14:59
0d9c442
Compare
Choose a tag to compare

reverts the changes made in 2.36.0 due to some reported breaks.

2.36.0

04 Mar 19:20
5bd1e3f
Compare
Choose a tag to compare
  • improve performance by reducing another iteration in processing query results and returning earlier

2.35.0

01 Mar 19:54
c29eaa7
Compare
Choose a tag to compare
  • overhaul internal caching strategy for better performance and fix cache miss when permission names contained spaces
  • deprecated hasUncachedPermissionTo() (use hasPermissionTo() instead)
  • added getPermissionNames() method

1.18.0

01 Mar 19:42
Compare
Choose a tag to compare

Support Laravel 5.8

Changed gate registration to use Authorizable contract, instead of Authenticatable

2.34.0

26 Feb 21:26
10f6b2e
Compare
Choose a tag to compare

Add explicit pivotKeys to role/permission Model BelongsToMany relationships

Ref #615 (comment)

2.33.0

20 Feb 15:56
9da0a16
Compare
Choose a tag to compare

Preliminary Laravel 5.8 compatibility

2.32.0

13 Feb 16:05
a6ddad0
Compare
Choose a tag to compare
  • Fix duplicate permissions being created through artisan command

2.31.0

04 Feb 03:57
5f99608
Compare
Choose a tag to compare
  • Add custom guard query to role scope
  • Remove use of array_wrap helper function due to future deprecation

2.30.0

28 Jan 23:54
6074481
Compare
Choose a tag to compare
  • Change cache time to DateInterval instead of integer(minutes)

This is in preparation for compatibility with Laravel 5.8's cache TTL change to seconds instead of minutes.

NOTE: If you leave your existing config/permission.php file alone, then with Laravel 5.8 the 60 * 24 will change from being treated as 24 hours to just 24 minutes. Depending on your app, this may or may not make a significant difference. Updating your config file to a specific DateInterval will add specificity and insulate you from the TTL change in Laravel 5.8.

Refs:
https://laravel-news.com/cache-ttl-change-coming-to-laravel-5-8
laravel/framework@fd6eb89

2.29.0

16 Dec 00:50
7f30880
Compare
Choose a tag to compare

Fix bound saved event from firing on all subsequent models when calling assignRole or givePermissionTo on unsaved models.
However, it is preferable to save the model first, and then add roles/permissions after saving. See #971.