Wolfgang Walther
edbd2a3dca
These don't really make sense, because it's non-trivial to construct a build plan that *ensures* the dependency that renovate creates a PR for is tested with the latest version. Cabal might just select a build plan, that doesn't include the dependency, in which case we could just as well have no upper bounds at all. Since there is no good way to test these changes (I tried, a while ago!), let's just disable these PRs. They are more annoying than anything else.
29 lines
485 B
JSON
29 lines
485 B
JSON
{
|
|
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
|
"extends": [
|
|
"config:best-practices"
|
|
],
|
|
"baseBranchPatterns": [
|
|
"main",
|
|
"/^v[0-9]+/"
|
|
],
|
|
"rebaseWhen": "conflicted",
|
|
"pip_requirements": {
|
|
"enabled": false
|
|
},
|
|
"packageRules": [
|
|
{
|
|
"matchManagers": [
|
|
"haskell-cabal"
|
|
],
|
|
"enabled": false
|
|
},
|
|
{
|
|
"matchBaseBranches": [
|
|
"/^v[0-9]+/"
|
|
],
|
|
"groupName": "all dependencies"
|
|
}
|
|
]
|
|
}
|