Have you committed and pushed an up-to-date composer.lock file to your repo?
Could you try the steps here to deploy in a manner that avoids cached composer files? If it works, you should be able to go back to regular deploys.
Have you committed and pushed an up-to-date composer.lock file to your repo?
Could you try the steps here to deploy in a manner that avoids cached composer files? If it works, you should be able to go back to regular deploys.