Recipe version conflicts with SS 4.2 #4
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi. Have some problems when I try to install with Silverstripe 4.2:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: remove silverstripe/recipe-cms 4.2.1
- Conclusion: don't install silverstripe/recipe-cms 4.2.1
- toastnz/silvershop-api 4.1.0 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.1 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.2 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.3 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.4 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.5 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.6 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.7 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.8 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- toastnz/silvershop-api 4.1.9 requires silverstripe/recipe-cms ^1.0.3 -> satisfiable by silverstripe/recipe-cms[1.0.x-dev, 1.1.x-dev, 1.x-dev, 1.2.x-dev].
- Can only install one of: silverstripe/recipe-cms[1.0.x-dev, 4.2.1].
- Can only install one of: silverstripe/recipe-cms[1.1.x-dev, 4.2.1].
- Can only install one of: silverstripe/recipe-cms[1.x-dev, 4.2.1].
- Can only install one of: silverstripe/recipe-cms[1.2.x-dev, 4.2.1].
- Installation request for silverstripe/recipe-cms (locked at 4.2.1, required as ^4.2) -> satisfiable by silverstripe/recipe-cms[4.2.1].
- Installation request for toastnz/silvershop-api ^4.1 -> satisfiable by toastnz/silvershop-api[4.1.0, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.1.5, 4.1.6, 4.1.7, 4.1.8, 4.1.9].
Just allowing CMS ^4 fixes this I think. It's the same way as Silvershop Core does.