54cd3ebbe3
I noticed we weren't getting updates and I think the core problem here is renovate was only triggering on the devel compose. But we just "floated" to whatever was found in the production compose as a base. Also we had a random copr. Drop that stuff, and just pin on the production compose.
47 lines
1.2 KiB
JSON
47 lines
1.2 KiB
JSON
{
|
|
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
|
"extends": [
|
|
"local>centos/.github:renovate-config"
|
|
],
|
|
"customDatasources": {
|
|
"c9s-compose": {
|
|
"defaultRegistryUrlTemplate": "https://composes.stream.centos.org/production/",
|
|
"format": "html"
|
|
}
|
|
},
|
|
"customManagers": [
|
|
{
|
|
"customType": "regex",
|
|
"fileMatch": [
|
|
"c9s.repo",
|
|
"centos-bootc-config.json"
|
|
],
|
|
"matchStrings": [
|
|
"https://composes.stream.centos.org/production/(?<currentValue>.*)/compose/(.*)",
|
|
"\"redhat.compose-id\": \"(?<currentValue>.*)\""
|
|
],
|
|
"datasourceTemplate": "custom.c9s-compose",
|
|
"depNameTemplate": "CentOS-Stream-9",
|
|
"versioningTemplate": "regex:^CentOS-Stream-9-(?<major>\\d{8})\\.d\\.0$"
|
|
}
|
|
],
|
|
"packageRules": [
|
|
{
|
|
"matchDatasources": [
|
|
"custom.c9s-compose"
|
|
],
|
|
"extractVersion": "(?<version>.+)/$",
|
|
"automerge": true,
|
|
"schedule": [
|
|
"at any time"
|
|
],
|
|
"groupName": null
|
|
},
|
|
{
|
|
"matchPackageNames": [
|
|
"quay.io/centos-bootc/bootc-image-builder"
|
|
],
|
|
"pinDigests": false
|
|
}
|
|
]
|
|
}
|