This manager was recently introduced to renovate and is now creating PRs for upper version bounds of our haskell dependencies. We still need to figure out how to deal with those in the best way, but some basic configuration can already be done. Here, we: - disallow any of those updates on the backbranches. - group GHC-provided dependencies together. - group packages from the hasql ecosystem together. - the fuzzyset dependency must be restricted to <0.3 - we know that already and did that on purpose.
41 lines
1.0 KiB
JSON
41 lines
1.0 KiB
JSON
{
|
|
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
|
"extends": [
|
|
"config:best-practices"
|
|
],
|
|
"baseBranches": [
|
|
"main",
|
|
"/^v[0-9]+/"
|
|
],
|
|
"rebaseWhen": "conflicted",
|
|
"pip_requirements": {
|
|
"enabled": false
|
|
},
|
|
"packageRules": [
|
|
{
|
|
"matchBaseBranches": [ "/^v[0-9]+/" ],
|
|
"matchManagers": ["haskell-cabal"],
|
|
"enabled": false
|
|
},
|
|
{
|
|
"matchBaseBranches": [ "/^v[0-9]+/" ],
|
|
"groupName": "all dependencies"
|
|
},
|
|
{
|
|
"matchManagers": ["haskell-cabal"],
|
|
"matchPackageNames": ["base", "bytestring", "containers", "directory", "mtl", "parsec", "process", "text"],
|
|
"groupName": "GHC dependencies"
|
|
},
|
|
{
|
|
"matchManagers": ["haskell-cabal"],
|
|
"matchPackageNames": ["hasql", "hasql-dynamic-statements", "hasql-notifications", "hasql-transaction", "hasql-pool"],
|
|
"groupName": "hasql"
|
|
},
|
|
{
|
|
"matchManagers": ["haskell-cabal"],
|
|
"matchPackageNames": ["fuzzyset"],
|
|
"allowedVersions": "<0.3"
|
|
}
|
|
]
|
|
}
|