Declaring PHP version >= forces PHP 5.6.0RC4 instead of 5.5.16 about heroku-buildpack-php HOT 5 CLOSED

What was the problem / solution?

from heroku-buildpack-php.

I should have looked at the composer docs first. Turns out you can have
multiple clauses in the version specification, so I just changed the
requirement to ">=5.3.18,<5.6" and everything was happy again.

On Wed, Aug 27, 2014 at 10:34 AM, David Zülke [email protected]
wrote:

What was the problem / solution?

—
Reply to this email directly or view it on GitHub
#79 (comment)
.

from heroku-buildpack-php.

I'm assuming you had a "minimum-stability": "RC" somewhere too then? That selector in itself should not pick a release candidate. Can you show the relevant parts of your composer.json just to make sure there's no bug there?

from heroku-buildpack-php.

Ah, that explains it. For some reason minimum-stability is set to dev.
So, no bug, just a misunderstanding on my part.

I didn't write this package, so I'll have to find out why it's set up that
way from the maintainers.

On Wed, Aug 27, 2014 at 10:58 AM, David Zülke [email protected]
wrote:

I'm assuming you had a "minimum-stability": "RC" somewhere too then? That
selector in itself should not pick a release candidate. Can you show the
relevant parts of your composer.json just to make sure there's no bug
there?

—
Reply to this email directly or view it on GitHub
#79 (comment)
.

from heroku-buildpack-php.

They probably wanted a dev version of a certain package. In general, you should use stability flags instead so it doesn't pull in dev versions of everything. See https://igor.io/2013/02/07/composer-stability-flags.html for some guidance.

from heroku-buildpack-php.