- How do I install zareismail/nova-policy in a Laravel Nova project?
- Install it with Composer using composer require zareismail/nova-policy, then confirm the package's service provider is registered (Laravel auto-discovery usually handles this). Because v2.0.0 targets Laravel Nova 4, make sure your application is already on Nova 4 before installing. Review the package's composer.json for Laravel and PHP constraints and run your test suite after installation.
- Does nova-policy v2.0.0 support Laravel Nova 3?
- The only release note for v2.0.0 is "Upgrade to nova 4," which strongly suggests v2 is built for Nova 4 and drops Nova 3 support. If your application still runs Nova 3, you should stay on the v1.x line or plan a coordinated Nova upgrade first. There is no published compatibility matrix, so verify against the package's composer.json before committing.
- What breaking changes are included in nova-policy v2.0.0?
- The release note only says "Upgrade to nova 4," so the exact breaking changes are not documented. A major version bump tied to Nova 4 likely means dropped Nova 3 support plus possible API, service provider, or asset changes. Inspect the diff between v1.x and v2.0.0 in the repository and run application smoke tests before upgrading.
- Which Laravel and PHP versions does nova-policy require?
- The package does not publish a compatibility matrix, so the authoritative source is its composer.json. Nova 4 itself requires PHP 8.0+ and a recent Laravel release, and the package will typically mirror those constraints. Check both the require and require-dev sections before adding it to your project.
- How do I migrate from nova-policy v1.x to v2.0.0?
- There is no official migration guide, so plan a staged upgrade: first move your application and Laravel Nova to version 4 in a staging environment, then update the package constraint to ^2.0. Review the package source for renamed classes, changed method signatures, or published assets that need republishing. Run your authorization tests and Nova smoke tests before deploying to production.
- What does nova-policy actually do for authorization in Laravel Nova?
- It is a Nova tool that helps you generate and organize policy classes for your Nova resources, so you can control who may view, create, update, and delete records from within Nova. It builds on Laravel's native policy and gate system rather than replacing it. Use it to keep policy files consistent across many resources instead of writing them by hand.
- Is zareismail/nova-policy actively maintained?
- Maintenance cadence is not documented; the v2.0.0 release note is only "Upgrade to nova 4," which suggests release notes and documentation are thin. Check the GitHub commit history, open issues, and response times before adopting it in a long-lived project. If activity is low, budget for forking the package or replacing it if a future Nova release breaks compatibility.
- Can I use nova-policy without Laravel Nova?
- No. It is a Laravel Nova integration, so it only makes sense in applications that already run Nova 4 as an admin panel. If you are not using Nova, use Laravel's built-in policies and gates directly, or a permissions package such as spatie/laravel-permission.
- How should I test policies generated by nova-policy?
- Test the underlying Laravel policies with feature tests that assert gate and policy checks for each role, and add Nova endpoint tests for view, create, update, and delete actions. Run the package's own test suite if it ships one, and verify behavior after every Nova or package upgrade. Because CI status is not documented, treat your own tests as the primary safety net.
- What are the alternatives to nova-policy for managing Nova permissions?
- Laravel's native policies and gates, Laravel Nova's built-in nova:policies Artisan command, and role/permission packages like spatie/laravel-permission are the main alternatives. nova-policy is mainly a convenience for generating and organizing policy classes across resources. Compare it against these options based on how many resources you have and whether you need role-based permissions beyond simple policies.