sylius/sylius composer constraint prevents sylius upgrade

[stefandoorn]

I'm trying to upgrade Sylius to dev-master (from beta.2), but requiring the CmsPlugin leads to:

Loading composer repositories with package information
Updating dependencies (including require-dev)                                      
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - lakion/cms-plugin dev-master requires sylius/sylius 1.0.0-beta.2 -> satisfiable by sylius/sylius[v1.0.0-beta.2] but these conflict with your requirements or minimum-stability.
    - lakion/cms-plugin dev-master requires sylius/sylius 1.0.0-beta.2 -> satisfiable by sylius/sylius[v1.0.0-beta.2] but these conflict with your requirements or minimum-stability.
    - lakion/cms-plugin dev-master requires sylius/sylius 1.0.0-beta.2 -> satisfiable by sylius/sylius[v1.0.0-beta.2] but these conflict with your requirements or minimum-stability.
    - Installation request for lakion/cms-plugin dev-master -> satisfiable by lakion/cms-plugin[dev-master].

My minimum stability is set to 'dev'. Is there a way to still load dev-master of Sylius while keeping dev-master of this package?

[michalmarcinkowski]

Try to change composer.json of CmsPlugin to ^1.0.0-beta.2@dev should help.

[stefandoorn]

Alright, did that in my fork (using dev-master, but it's similar I think), but should I PR that?

[michalmarcinkowski]

Then we would need to wait for 1.0.0 stable to release CmsPlugin. I need to give few more thoughts on CmsPlugin release plan.

[gnsimoes]

Can you change the composer.json file to be able to use with Sylius beta 3?

[Mipme]

Are there already any experiences with the CMS on beta.3? Would need the plugin sooner than later...

[stefandoorn]

Could this plugin be made compatible with 1.0? :-) If there are any PR's needed (besides the ones in there already), I can see if I can support a bit.

[michalmarcinkowski]

I think there shouldn't be much work. Replied to your PR, let's see.