Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

composer_version documentation should specify to nullify composer_version_branch #77

Closed
brandonsavage opened this issue Jan 3, 2022 · 5 comments
Labels

Comments

@brandonsavage
Copy link

Composer recently released version 2.2 which includes BC breaking changes. However, limiting the version with composer_version doesn't seem to do anything.

My specific configuration:

composer_version: '2.1.14'

What I get when I run composer --version:

root@ansible-testing-2022-brandon:~# composer --version
Do not run Composer as root/super user! See https://getcomposer.org/root for details
Continue as root/super user [yes]? yes
Composer version 2.2.3 2021-12-31 12:18:53
@brandonsavage brandonsavage changed the title composer_version does not limit version composer_version documentation should specify to nullify composer_version_branch Jan 3, 2022
@brandonsavage
Copy link
Author

It appears my mistake was not nullifying the composer_verrsion_branch parameter. The documentation should be more explicit. I'll see if I can make a PR but I filed this to keep track in case I forget.

@gdubicki
Copy link
Contributor

Hi @brandonsavage! I was just hit by the same thing and I created #79 to prevent this in the future.

@gdubicki
Copy link
Contributor

gdubicki commented Mar 30, 2022

Kind of duplicates #72.

@stale
Copy link

stale bot commented Jul 10, 2022

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@stale stale bot added the stale label Jul 10, 2022
@gdubicki
Copy link
Contributor

This is fixed in 1.9.2 and can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants