mirror of
https://github.com/civitai/civitai.git
synced 2026-09-20 22:08:18 +08:00
Zachary Lowden
0f9b8a79bc
Renovate's first scheduled run queued three major bumps at once: clickhouse-server v26, node v24, and postgres v18. The node one rewrites the base image of every service under apps/ plus containers/image-stub in a single PR titled "update node.js to v24". Majors now require an explicit tick on the Dependency Dashboard before a branch or PR is created. They stay listed there, so nothing becomes invisible. Digest pins and patch/minor updates are separate updateTypes and keep flowing automatically.
19 lines
1.3 KiB
JSON
19 lines
1.3 KiB
JSON
{
|
|
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
|
"extends": ["config:recommended", "docker:pinDigests"],
|
|
"enabledManagers": ["dockerfile", "nvm"],
|
|
"schedule": ["before 6am on monday"],
|
|
"major": {
|
|
"description": "A major bump is never opened unasked. Majors stay VISIBLE on the Dependency Dashboard (issue #3789) with an unticked checkbox, and a branch/PR is only created once a human ticks it. Digest pins and patch/minor updates are unaffected and keep flowing automatically — they are separate updateTypes. Motivation: the first scheduled run queued three majors at once, one of which (node v24) rewrites the base image of every service under apps/ plus containers/image-stub in a single PR.",
|
|
"dependencyDashboardApproval": true
|
|
},
|
|
"packageRules": [
|
|
{
|
|
"description": "Keep the root Dockerfile's node tag and .nvmrc in ONE pull request. src/__tests__/node-version-consistency.test.ts asserts the two agree, so a bump that moves only one of them reds that guard. Scoped to the two files that guard actually reads: the per-service images under apps/ and containers/ are on their own cadence and must not be dragged into this group.",
|
|
"matchDepNames": ["node"],
|
|
"matchFileNames": ["Dockerfile", ".nvmrc"],
|
|
"groupName": "node runtime pin"
|
|
}
|
|
]
|
|
}
|