Use Composer’s --with flag to force an update together, allowing Composer to resolve dependencies in one shot:
composer update laravel/nova nova-kit/nova-packages-tool --with=laravel/nova,nova-kit/nova-packages-tool
Hello,
I'm trying to update Nova from 4.26.5 to the latest ^4.0 release (4.35.10 currently).
Trying this:
composer update laravel/nova
...does nothing, specifically:
"Nothing to install, update or remove"
In composer.json, I have the standard: "laravel/nova": "^4.0"
Just learned about 'composer why-not', so I tried that:
composer why-not laravel/nova 4.35.10
which gives:
nova-kit/nova-packages-tool v1.11.2 requires laravel/nova (>=4.26.5 <4.27.0)
Now nova-kit/nova-packages-tool is not in composer.json; appears to be a dependency for other packages.
When I try to update nova-kit/nova-packages-tool, it requires a later version of Nova:
composer why-not nova-kit/nova-packages-tool 1.17
nova-kit/nova-packages-tool v1.17.0 requires laravel/nova (>=4.35.0 <4.36.0)
Now I seem to be stuck in a catch-22 where each package keeps the other from updating.
I've updated from Nova 3 > Nova 4 and to several Nova 4 minor versions before, but have never seen this problem.
No doubt it's something simple but at the moment I'm stumped. Any ideas?
Please or to participate in this conversation.