Using ~3.0 pulls 3.1 about app HOT 15 CLOSED

Doesn't happen for me. Tried both an existing project and a new project. For the existing project I did clear the cache, remove the composer.lock and deleted the vendor files. Get 3.0.10 for both the new and existing project.

from app.

What is your minimum-stability value?

from app.

For me, I have "minimum-stability": "dev"

from app.

@davidyell Could you possibly post your complete composer.json? My guess is still that there's something wrong in there, maybe in the require-dev which overrules the require?

from app.

    "require-dev": {
      "cakephp/cakephp-codesniffer": "~2.0",
      "cakephp/bake": "~1.0"
    },

So unless one of these has a dependancy of 3.1

from app.

(3.1.x-dev a87c87f)

a87c87f is not even current HEAD of 3.1 branch.

from app.

I've kinda sidestepped the issue by using 3.0.* in the project now, but I thought that it might affect others. I guess not 😕

from app.

With "minimum-stability": "dev" isnt that expected behavior? Removing that should only pull stable versions.

from app.

But "minimum-stability": "dev" is what you get by default if you create a new CakePHP project. And that definitely won't give you unstable branches by default.

from app.

Was looking at my composer.json again and spotted the "prefer-stable": true. Did you happen to change or got rid of this? When I change it to false, it does go to 3.1.x-dev c5990f9.

from app.

So make of this what you will.

https://github.com/cakephp/app/blob/master/composer.json#L38-L39

from app.

Can't really make anything of that, that just confirms everything I said. 👍

from app.

We can then probably close this as we now know how to prevent 3.1 to be pulled :)

from app.

Reading compiser docs today, ~3.0 will get you ~3.x whereas ~3.0.0 wil get you 3.0.x - also ^3.0 should work getting you 3.0.x afair. For me those also get unstable versions btw.

from app.

@jhli You will get unstable versions with ~3.0 if you have the minimum-stability set to dev or beta.

from app.