Unsure about require and conflicts #12384
-
I got a email which tells that we not longer can use require and conflict which is a very common usecase for us:
Strangely if I run Whole EmailThe sulu/sulu package of which you are a maintainer has It is recommended that you use Below is the update log which should highlight errors as [Composer\Repository\InvalidRepositoryException]: Some branches contained invalid data and were discarded, it is advised to review the log and fix any issues present in branches Skipped branch 2.6, Invalid package information: Skipped branch 2.5, Invalid package information: Skipped branch 3.0, Invalid package information: Updated from https://github.com/sulu/sulu using Composer\Repository\Vcs\GitHubDriver For us it is very common that I require a specific min version based on our used feature set, and conflicting maybe some release which did break something: {
"require": {
"doctrine/orm": "^2.13",
"gedmo/doctrine-extensions": "^3.0.4",
"jms/serializer-bundle": "^4.0.1 || ^5.0",
},
"conflict": {
"doctrine/doctrine-bundle": "2.13.1 || 2.13.x-dev || 2.14.x-dev",
"gedmo/doctrine-extensions" : "3.7.0",
"jms/serializer-bundle": "3.9.0 || 4.1.0"
}
} |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
There is an attempt to make this a warning: #12377 But that PR isnβt merged yet. |
Beta Was this translation helpful? Give feedback.
-
Sorry that's entirely my fault, accidentally put this in prod while trying something out π It's resolved now and the package is not in broken state anymore. |
Beta Was this translation helpful? Give feedback.
-
Would also like to add for anyone else who got this email: there is no need to act. I personally don't think this should even cause a warning and no final decision on this has been made. |
Beta Was this translation helpful? Give feedback.
Sorry that's entirely my fault, accidentally put this in prod while trying something out π It's resolved now and the package is not in broken state anymore.