Let the self-hosted Renovate bot authenticate to the code.emmathe.dev container registry so it can read and update digests for the private images pinned in the Terraform repo — whyisthedlrshut.today (dlr) and docs-site. Without this, Renovate can't reach those images and the digests never get bumped (they stay pinned but stale).
Scoped to the docker datasource only — the existing Gitea platform/git auth is untouched.
Digest updates already automerge (packageRules) and pinDigests is on (config:best-practices), so once auth works these images auto-bump.
Owner action: create the secret and expose it to the bot as the env var RENOVATE_REGISTRY_TOKEN — a Gitea PAT (user renovate-bot, or adjust the username in the rule) with read:package scope. That's the only thing needed.
The images are matched by the Terraform repo's existing customManager (docker datasource on variables.tf); no change needed there.
Let the self-hosted Renovate bot authenticate to the `code.emmathe.dev` container registry so it can read and update digests for the **private** images pinned in the Terraform repo — `whyisthedlrshut.today` (dlr) and `docs-site`. Without this, Renovate can't reach those images and the digests never get bumped (they stay pinned but stale).
- Adds a `hostRules` entry: `matchHost: code.emmathe.dev`, `hostType: docker`, `username: renovate-bot`, `password: process.env.RENOVATE_REGISTRY_TOKEN`.
- Scoped to the docker datasource only — the existing Gitea platform/git auth is untouched.
- Digest updates already `automerge` (packageRules) and `pinDigests` is on (config:best-practices), so once auth works these images auto-bump.
**Owner action:** create the secret and expose it to the bot as the env var **`RENOVATE_REGISTRY_TOKEN`** — a Gitea PAT (user `renovate-bot`, or adjust the `username` in the rule) with **`read:package`** scope. That's the only thing needed.
The images are matched by the Terraform repo's existing `customManager` (docker datasource on `variables.tf`); no change needed there.
Add a docker hostRule so Renovate can read/update digests for private images
(dlr, docs-site) pinned in the Terraform repo. Token via RENOVATE_REGISTRY_TOKEN env.
Add a docker hostRule so Renovate can read/update digests for private images
(dlr, docs-site) pinned in the Terraform repo. Token via RENOVATE_REGISTRY_TOKEN env.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Let the self-hosted Renovate bot authenticate to the
code.emmathe.devcontainer registry so it can read and update digests for the private images pinned in the Terraform repo —whyisthedlrshut.today(dlr) anddocs-site. Without this, Renovate can't reach those images and the digests never get bumped (they stay pinned but stale).hostRulesentry:matchHost: code.emmathe.dev,hostType: docker,username: renovate-bot,password: process.env.RENOVATE_REGISTRY_TOKEN.automerge(packageRules) andpinDigestsis on (config:best-practices), so once auth works these images auto-bump.Owner action: create the secret and expose it to the bot as the env var
RENOVATE_REGISTRY_TOKEN— a Gitea PAT (userrenovate-bot, or adjust theusernamein the rule) withread:packagescope. That's the only thing needed.The images are matched by the Terraform repo's existing
customManager(docker datasource onvariables.tf); no change needed there.