Closed stefandoorn closed 7 years ago
Try to change composer.json of CmsPlugin to ^1.0.0-beta.2@dev
should help.
Alright, did that in my fork (using dev-master, but it's similar I think), but should I PR that?
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.
Can you change the composer.json file to be able to use with Sylius beta 3?
Are there already any experiences with the CMS on beta.3? Would need the plugin sooner than later...
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.
I think there shouldn't be much work. Replied to your PR, let's see.
I'm trying to upgrade Sylius to dev-master (from beta.2), but requiring the CmsPlugin leads to:
My minimum stability is set to 'dev'. Is there a way to still load
dev-master
of Sylius while keepingdev-master
of this package?