stale[bot]
commented
1 year ago This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please update it if any action still required.
Your issue may already be reported! Please search on the issue tracker before creating one.
Expected Behavior
Set a variable in the docker yaml to specify which composer version to install. Upon running the image, that version is then used instead of the latest.
Current Behavior
The latest released composer version is installed.
Context
Recently, composer 2.5.x has been released with some breaking changes. One being that vendor packages must not have, or have a valid composer.lock.
One of the packages I need to install, has an invalid composer.lock and my CI/CD fails. This could be fixed by locking the composer version to 2.4.x for the time being.
Your Environment