Version issue during install of a fresh Symfony 4 (3.3 vs 3.4) about maker-bundle HOT 5 CLOSED

Closing as it will be self resolved by today's releases

from maker-bundle.

Well, the error message is clear:

The requested package symfony/config ^3.4|^4.0 is satisfiable by
symfony/config[3.4.x-dev, 4.0.x-dev, 4.1.x-dev, v3.4.0-BETA1, v3.4.0-BETA2, v3.4.0-BETA3, v3.4.0-BETA4, v3.4.0-RC1, v3.4.0-RC2, v4.0.0-BETA1, v4.0.0-BETA2, v4.0.0-BETA3, v4.0.0-BETA4, v4.0.0-RC1, v4.0.0-RC2]
but these conflict with your requirements or minimum-stability.

Symfony 3.4 and 4.0 are not stable yet (they will become stable in a few hours). Until it is stable, you have to tell composer that it is fine to use unstable versions (by default, they are forbidden).

from maker-bundle.

If you install Symfony 4 from scratch

What do you mean by this step ? How are you installing Symfony 4 ?

from maker-bundle.

I got this working by either using minimum-stability: RC or installing symfony using the beta channel. (Recommended here: symfony/skeleton#36 (comment))

What i meant in my OP is that installing Symfony 4.0 using the docs on the live site (at the time of my post) causes these issues. I understand some modules are not stable yet (as not released) but some seem to be already in stable? (eg they're the ones Composer downloads).

So some packages that are "stable" depend on unstable dependencies... eg:

• Symfony skeleton (stable) 3.3 installs stable Config 3.3
• Doctrine and Maker "Stable" (assuming it is because that is what composer is defaulting to based on my minimum stability) both depend on Config 3.4 which is not stable.

This likely an non-issue after today though when all repos become "stable", I guess it's just bad timing to start doing a fresh Symfony install a day before the release :D

from maker-bundle.

Yep, we’re just waiting for the stable releases. Indeed, the install doesn’t quite work right currently because of this :)

from maker-bundle.