-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Composer] Allowed ezpublish-kernel ^7.0 #24
Conversation
+1, but you probably dont need to set dev, as usual that will be set in meta |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistent space usage compared to the line below, but I don't know which is correct..
1921d28
to
f0d46d1
Compare
@@ -10,7 +10,7 @@ | |||
} | |||
], | |||
"require": { | |||
"ezsystems/ezpublish-kernel": "^6.2", | |||
"ezsystems/ezpublish-kernel": "^6.2 || ^7.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Inconsistent space usage compared to the line below, but I don't know which is correct..
It seems none :) This probably is due to some changes in composer.json format. Right now doc mentions only double pipe ||
surrounded by spaces, so I aligned this with it.
Thanks for pointing this out @glye
…24) * [Rebranding] Expose raw edition identifier getter as a static method * fix: Coding Standards
This PR allows
ezpublish-kernel:^7.0@dev
forez-support-tools
.Reason: Right now we have to make workaround to install
ezplatform:2.0
meta-repository dependencies by setting requirement forezpublish-kernel
in the form of7.0.x-dev as 6.99.x-dev
instead of simply^7.0@dev
. This change solves that partially (see also: ezsystems/ezplatform-http-cache#16).