9d876a58a8
It was added in941e5f0(2024-09-21) as a cache-less variant, because the BuildKit cache mounts in the main Dockerfile were causing trouble in CI, and the workflow pointed at it with `file: Dockerfile.ci`. That line was removed in6719538(2025-02-27, "Switch to using native ARM64 builders"), which returned the build to the default Dockerfile - but the file itself stayed behind. Nothing has referenced it since. It had meanwhile drifted from the real Dockerfile (no RELEASE_BUILD argument, no cache mounts) while Renovate kept bumping its base image pin, so every one of those bumps was a pull request for a file that is never built. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
67 lines
2.1 KiB
JSON
67 lines
2.1 KiB
JSON
{
|
|
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
|
|
"extends": [
|
|
"config:recommended"
|
|
],
|
|
"labels": [
|
|
"dependencies"
|
|
],
|
|
"packageRules": [
|
|
{
|
|
"description": "Cargo dependencies, the Rust toolchain pin, prek (via mise) and the workflows' own actions merge by pushing to main, without a pull request. ci.yml runs on `push: [\"**\"]`, so the Renovate branch itself is compiled, linted with `clippy -D warnings` and unit-tested first; a failure leaves the branch red and Renovate raises a pull request instead of merging.",
|
|
"matchManagers": [
|
|
"cargo",
|
|
"rust-toolchain",
|
|
"mise",
|
|
"github-actions"
|
|
],
|
|
"matchUpdateTypes": [
|
|
"minor",
|
|
"patch",
|
|
"digest"
|
|
],
|
|
"automerge": true,
|
|
"automergeType": "branch",
|
|
"platformAutomerge": false
|
|
},
|
|
{
|
|
"description": "The release image's base (Dockerfile). Gated by ci.yml's docker-build job, which builds the image exactly as Publish does but with `push: false`, and which only runs when the Dockerfile actually changed.",
|
|
"matchManagers": [
|
|
"dockerfile"
|
|
],
|
|
"matchUpdateTypes": [
|
|
"minor",
|
|
"patch",
|
|
"digest"
|
|
],
|
|
"automerge": true,
|
|
"automergeType": "branch",
|
|
"platformAutomerge": false
|
|
},
|
|
{
|
|
"description": "Local development service images under etc/services/** - the homeservers and LLM backends that `just services-start` brings up. They are never part of a shipped artifact and CI does not run them, so the justification here is blast radius rather than validation: the worst case is a broken local development stack, fixed by pinning back.",
|
|
"matchManagers": [
|
|
"docker-compose"
|
|
],
|
|
"matchFileNames": [
|
|
"etc/services/**"
|
|
],
|
|
"matchUpdateTypes": [
|
|
"minor",
|
|
"patch",
|
|
"digest"
|
|
],
|
|
"automerge": true,
|
|
"automergeType": "branch",
|
|
"platformAutomerge": false
|
|
},
|
|
{
|
|
"description": "Major updates always get a pull request and a human. This is deliberately the last rule so that it overrides the automerge rules above for every manager.",
|
|
"matchUpdateTypes": [
|
|
"major"
|
|
],
|
|
"automerge": false
|
|
}
|
|
]
|
|
}
|