Closed axl89 closed 4 years ago
I hit this today also.
Yeah this was caused by the composer project they changed composer.phar from being the stable build to being a dev snapshot. They don't feel its a BC break because they don't support downloading directly and suggest everyone uses their install script.
Hi all, thanks for opening this issue!
@aashley is right, this didn't use to be a dev composer build at that endpoint...
Solution? Ad hoc, I'd suggest using a wrapper cookbook (for anyone running into the issue right now) and re-pointing to the stable endpoint. A proper fix will go out when I have a moment to make the (tiny) change...
Hope this helps!
@djoos would you accept a PR to change this?
Hi @caryp,
Thanks for the offer!
I've actually shipped it out in v2.7.0 - however, my "fixes #79" didn't seem to have kicked in, apologies for it hence not referencing the commit (f14c0fa50e9359edf42254c062c9a8b3f0dfac90) here...
Kind regards, David
With the default attribute:
It's downloading the
2.0-dev
version of composer:I think having an unstable version of composer by default should not be the default behavior, so I suggest the attribute to be changed to: