You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently deploy:vendors uses bin/composer option which downloads the latest Composer binary on every deploy. This can lead to unexpected breaking changes. For example, 1.10.0 started to output a lot of deprecation warnings in my case
There are lots of easy workarounds (override bin/composer option, use pre-installed Composer, etc.). But it would be nice to just add something like set('composer_version', '1.9.3'). Or just save composer binary somewhere between deploys (maybe in .dep dir)
The text was updated successfully, but these errors were encountered:
Currently
deploy:vendors
usesbin/composer
option which downloads the latest Composer binary on every deploy. This can lead to unexpected breaking changes. For example, 1.10.0 started to output a lot of deprecation warnings in my caseThere are lots of easy workarounds (override
bin/composer
option, use pre-installed Composer, etc.). But it would be nice to just add something likeset('composer_version', '1.9.3')
. Or just save composer binary somewhere between deploys (maybe in.dep
dir)The text was updated successfully, but these errors were encountered: