Nova Permission Laravel Package

Product Decisions This Supports

• Dependency upgrade planning: v4.0.0 is primarily a compatibility release adding PHP 8.1 and laravel-permission 5 support. This supports decisions to keep the permission layer current with the Laravel stack and avoid being blocked on future framework or security upgrades.
• Roadmap sequencing: If the product roadmap includes Laravel/PHP modernization, this release should be scheduled as part of that workstream rather than treated as a standalone feature. Teams still on PHP 8.0 or laravel-permission 4 should plan a migration path before adopting v4.
• Build vs. buy: If the product needs standard role/permission integration in Laravel, using this package is preferable to custom permission glue code, provided the team is already standardized on laravel-permission v5 and PHP 8.1+. Custom builds increase maintenance burden and slow upgrades.
• Use cases: Supports RBAC-style authorization, role and permission management, and Laravel applications that depend on laravel-permission. It is an infrastructure/enabler package, not a user-facing feature differentiator.
• Release risk decision: Treat v4.0.0 as a major-version upgrade. It is low-feature but potentially breaking for consumers on older PHP or laravel-permission versions, so adoption should follow compatibility verification rather than automatic upgrade.

When to Consider This Package

• Consider adoption when:
  • The application runs PHP 8.1 or later.
  • The application uses or plans to use laravel-permission v5.
  • The team wants maintained integration rather than custom permission wiring.
  • The product roadmap includes Laravel/PHP upgrades and reducing dependency debt.
  • Engineering can validate composer constraints, authorization behavior, and role/permission migrations in staging.
• Look elsewhere or defer when:
  • The application is pinned to PHP 8.0 or earlier.
  • The application depends on laravel-permission v4 or earlier and cannot migrate yet.
  • The product does not use Laravel’s permission/role model, or authorization needs are minimal enough for native Laravel gates/policies.
  • The package’s maintenance cadence, documentation, or test coverage is insufficient for a security-sensitive authorization dependency.
  • A major-version upgrade cannot be absorbed before upcoming release deadlines without a rollback plan.

How to Pitch It (Stakeholders)

Executive summary: v4.0.0 is a compatibility-focused major release that adds PHP 8.1 and laravel-permission 5 support. It is not a new product capability; it reduces platform risk and keeps the authorization layer aligned with the modern Laravel stack. The main decision is whether to schedule the upgrade now or intentionally defer it until PHP/laravel-permission migration work is funded.

Engineering summary: Upgrade only after confirming PHP 8.1+ and laravel-permission v5 constraints. Because this is a major version, treat it as a migration: review changelog, run authorization/role-permission regression tests, verify composer dependency resolution, and validate rollback. If the team is already on the supported stack, adopting v4.0.0 is a low-cost maintenance win. If not, defer and plan the PHP/laravel-permission upgrade as a prerequisite.