I'm unfortunately dealing with a very old system that hasn't been updated in a long time. I've been able to update it up to 3.0.41.1 but once I attempt to go any further I get tons of different errors. They primarily seem to be migrations. I keep having to do a restore of the DB I'm working with over and over to try to sort this out but I'm not sure what else to be looking for.
Any recommendations? (besides updating things at the right time?)
UPDATE 1:
When attempting to update from the web interface (which i think attempts to go straight to 3.4.5) I consistently get the following error:
Composer output: Package "craftcms/vue-asset" listed for update is not installed. Ignoring.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for craftcms/cms 3.4.5 -> satisfiable by craftcms/cms[3.4.5].
- craftcms/cms 3.4.5 requires twig/twig ~2.12.0 -> satisfiable by twig/twig[v2.12.3, v2.12.2, v2.12.1, v2.12.0] but these conflict with your requirements or minimum-stability.
Problem 2
- spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -> satisfiable by craftcms/cms[3.4.5].
- spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -> satisfiable by craftcms/cms[3.4.5].
- spicyweb/craft-embedded-assets 2.0.12 requires craftcms/cms ^3.0.0 -> satisfiable by craftcms/cms[3.4.5].
- craftcms/cms 3.4.5 requires twig/twig ~2.12.0 -> satisfiable by twig/twig[v2.12.3, v2.12.2, v2.12.1, v2.12.0] but these conflict with your requirements or minimum-stability.
- Installation request for spicyweb/craft-embedded-assets 2.0.12 -> satisfiable by spicyweb/craft-embedded-assets[2.0.12].
Running update with --no-dev does not mean require-dev is ignored, it just means the packages will not be installed. If dev requirements are blocking the update you have to resolve those problems.
composer.json
file contents? – Brandon Kelly Feb 8 '20 at 13:35