I’ve spent good portions of a couple of days trying to update a site, and have worked my way through a few snags only to bump up against an issue that has me stumped.
Up to now:
- PHP upgrade & “vlucas/phpdotenv”: “^5.3”,
- A bunch of plugin updates in composer
- Upgrade Composer to v2 (Which required a terminal-based IPv6 workaround on staging)
- Updated Bedrock manually
- Remove hirak/prestissimo since it’s v1-specific (thx Twansparent)
- Everything works locally
- I can now re-provision staging using Ansible
- Running “composer --version” on the local vagrant box or on staging shows v2 is running
…but deploys to staging don’t work, with a failure at
TASK [deploy : Install Composer dependencies] The "composer/installers" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option. The "philippbaschke/acf-pro-installer" plugin was skipped because it requires a Plugin API version ("^1.0") that does not match your Composer installation ("2.0.0"). You may need to run composer update with the "--no-plugins" option.
But in both site/composer.json and site/web/app/themes/mytheme/composer.json, I’m specifying
which is a version of the package that is supposed to be compatible with Composer 2
And in my composer.json, I’ve also replaced “philippbaschke/acf-pro-installer” with “pivvenit/acf-pro-installer”, so it’s intriguing that the philippbaschke package is referenced.
This suggested to me that there might be a caching issue, and I’ve run “composer clear-cache” in /srv/www/mysite.com/current to no effect.
I’m at a bit of a loss here.
Thanks in advance.