v2.3.12

Full Changelog: v2.3.11...v2.3.12

v2.3.11

Full Changelog: v2.3.10...v2.3.11

v2.3.10

What's Changed

• Create lint.yml by @eramitgupta in #25

Full Changelog: v2.3.9...v2.3.10

v2.3.9

What's Changed

• Update README.md by @eramitgupta in #22
• feat: Update README.md by @eramitgupta in #23
• New feat Middleware by @eramitgupta in #24

Full Changelog: v2.3.8...v2.3.9

v2.3.8

New Features & Improvements:

1. Upgrade-Version Command:

   • Enhanced the erag:upgrade-version command to automatically update the package and publish new migration files.
   • Simplifies the upgrade process by integrating composer update erag/laravel-role-permission into the command for seamless updates.

2. Detach Permissions Functionality:

   • Added the detachPermissions method to enable removing one or multiple permissions from a user.
   • Supports various input formats, including arrays, pipe-separated strings, comma-separated strings, and single permission names.

Full Changelog: v2.3.7...v2.3.8

v2.3.7

Full Changelog: v2.3.6...v2.3.7

v2.3.6

What's Changed

Optional Expiration for Permissions

[Feature] Add expiration feature to permissions

• Added support for unlimited permissions with null expiration.
• Updated the seeder and helper methods to handle null expiration as "no expiration."
• Optimized code for performance improvements in permission management.
• Updated README with usage instructions and examples for the new feature.

This Laravel package introduces an optional expiration feature for permissions, allowing developers to assign roles and permissions to users with a specified expiration date. This functionality provides greater control over user access, enabling you to manage permissions dynamically based on your application's needs.

Features

• Optional Expiration Dates: When assigning permissions, you can optionally specify an expiration date.

• Flexible Management: Users can have multiple permissions, each with its own expiration date. This allows for granular control over user access based on changing requirements or time-limited privileges.

• Automatic Expiration Handling: The system automatically checks if a role or permission has expired. If permission is expired, it will be considered inactive, preventing access to protected resources.

Setting Expiration

If you don’t need an expiration, simply store null in the database:

• Feature/permissions expires by @eramitgupta in #21
  Full Changelog: v2.3.5...v2.3.6

v2.3.5

What's Changed

• feat: quick fixed by @eramitgupta in #20

Full Changelog: v2.3.4...v2.3.5

v2.3.4

What's Changed

• Add fillable in Permission/Role models by @johndivam in #19

New Contributors

• @johndivam made their first contribution in #19

Full Changelog: v2.3.3...v2.3.4

v2.3.3

What's Changed

• improve code or styling, add error handling, implement helper functions, and update documentation

• Update README.md by @AbhishekPriy9 in #16

New Contributors

• @AbhishekPriy9 made their first contribution in #16

Full Changelog: v2.3.2...v2.3.3