- How do I install bondgenoot/laravel-nova-news?
- Install it with Composer using composer require bondgenoot/laravel-nova-news, then register the tool in your Nova service provider. Publish and run the package migrations with php artisan vendor:publish and php artisan migrate. After that, clear your config and route caches and confirm the news resource appears in the Nova sidebar.
- What PHP version does laravel-nova-news require?
- Version 1.1.0 raises the PHP requirement from ^8.1 to ^8.2, so every environment including CI, cron, and queue hosts must run PHP 8.2 or newer. Version 1.0.5 remains usable on PHP 8.1. PHP 8.3 is a sensible choice for new work if the rest of your stack supports it.
- Which Laravel and Nova versions are supported by laravel-nova-news?
- The changelog does not publish an explicit compatibility matrix, so verify against your own stack rather than assuming. The 1.1.0 dev-dependency bump to Orchestra Testbench 8 implies Laravel 10-era framework support, and Nova 4 is the realistic target. Validate with composer why-not and a staging smoke test before merging.
- Does laravel-nova-news publish migrations and config files?
- It follows the standard Nova tool pattern: Composer require, tool registration, then vendor:publish for the package migration and configuration assets. Run php artisan vendor:publish and inspect the available tags for this package before running migrations. Because 1.1.0 is a dependency-only release, publish tags and asset build tooling should be unchanged from 1.0.5.
- How do I register the news tool in Laravel Nova?
- Add the package tool class to the tools() array in app/Nova/NovaServiceProvider.php, following the class name in the package documentation. Then clear cached config and routes so Nova picks up the new navigation entry. Confirm the resource shows in the sidebar and that your user account can access it.
- Does laravel-nova-news respect my Nova authorization policies?
- Yes, the package sits inside Nova's resource and authorization layer rather than creating a separate admin surface. It inherits Nova policies, navigation registration, and the asset pipeline, so existing gates and policy conventions apply. Review any published policy or permission settings if you need to restrict who can create or publish news posts.
- Is upgrading from 1.0.5 to 1.1.0 a breaking change?
- Functionally it should be identical to 1.0.5 because no PHP source changes are advertised in 1.1.0. The practical breaking change is the PHP floor moving to 8.2 inside a minor release, which will fail composer update on PHP 8.1 hosts. Treat the runtime upgrade as a prerequisite and upgrade PHP before bumping the package constraint.
- Why does composer update fail with a PHP constraint error after upgrading laravel-nova-news?
- Version 1.1.0 now requires PHP ^8.2, so Composer refuses to install it on an 8.1 runtime. Run composer why-not bondgenoot/laravel-nova-news to see which constraint is blocking the update. If you cannot upgrade PHP yet, pin the package to 1.0.5 explicitly so a routine composer update cannot pull 1.1.0.
- Can I use laravel-nova-news on Laravel 9 or PHP 8.1?
- Not on 1.1.0; applications still on Laravel 9 and PHP 8.1 should stay on the 1.0.x line. Upgrade the PHP runtime in CI and staging first, confirm the application boots and its own tests pass on 8.2, and only then raise the package constraint to ^1.1. Always sequence the platform upgrade before the package upgrade, never the reverse.
- How should I test a laravel-nova-news upgrade before production?
- Validate the matrix explicitly: PHP 8.2 or 8.3 with Laravel 10 or 11 and Nova 4. Then check Nova tool registration, news CRUD, media and upload handling, and any frontend views that read the package models. Because 1.1.0 ships no code changes, a green result on your existing 1.0.5 configuration under PHP 8.2 is strong evidence the upgrade is safe, and a red result points at the host environment rather than the package.