P7: Automate dependency updates with Renovate #67

Open
opened 2026-11-09 17:07:08 +00:00 by claude · 2 comments
Member

Run self-hosted Renovate as a scheduled Actions workflow against Gitea, to raise PRs for pinned charts, images, and actions.

Eric: create a dedicated bot account and token with limited repo access.
Claude: write the config and start with DevOps/www and ansible-role-gitea, capped to a few open PRs.

Acceptance: Renovate opens a correct update PR and respects the PR cap.

Depends on: P5, G11.

Run self-hosted Renovate as a scheduled Actions workflow against Gitea, to raise PRs for pinned charts, images, and actions. **Eric**: create a dedicated bot account and token with limited repo access. **Claude**: write the config and start with `DevOps/www` and `ansible-role-gitea`, capped to a few open PRs. **Acceptance**: Renovate opens a correct update PR and respects the PR cap. Depends on: P5, G11.
claude added this to the CI/CD 3: Build and publish milestone 2026-11-09 17:07:08 +00:00
claude added the needs-ericcicd labels 2026-11-09 17:07:08 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Owner

I have accounts for users gitea and gitea-actions. Would either of these be appropriate?

I have accounts for users gitea and gitea-actions. Would either of these be appropriate?
Author
Member

Short answer: neither. I recommend a new account just for Renovate.

What I found (read-only):

  • gitea-actions isn't a real account. It's Gitea's built-in identity for Actions: it shows as the actor on things a workflow does with its automatic job token. It can't sign in or hold a personal access token, and Renovate needs one.
  • gitea isn't a Gitea user either. A user search finds only gitea_admin. The name matches the mailer login in the Gitea role ([mailer] USER: gitea), so it's probably the directory or mail account Gitea sends email with. Using it for Renovate would give one credential a second purpose, which is what I5 (#47) is splitting up. A Renovate token also ends up in an Actions secret, so if it leaked, the mail account would leak with it.

Recommendation: a local Gitea user such as renovate-bot:

  • Not an admin, and not a member of any team with admin rights.
  • Added as a collaborator with Write only on the repos Renovate should touch. At first that's DevOps/www and DevOps/ansible-role-gitea. Write lets it push branches and open PRs. Branch protection from G11 (#59) keeps it from merging on its own.
  • One personal access token with the scopes write:repository, write:issue (for the dependency dashboard issue) and read:user, stored as a repo-level Actions secret RENOVATE_TOKEN in whichever repo runs the schedule.
  • Optionally a read-only GitHub token as RENOVATE_GITHUB_COM_TOKEN, so lookups of GitHub-hosted releases don't hit anonymous rate limits.

No rush. P7 depends on P5 (#65) and G11 (#59), and neither is done yet. When those are in place I'll write the config with a cap of two open PRs and ask for the account then. needs-eric stays for the account.

— eom-cicd-roadmap

**Short answer: neither. I recommend a new account just for Renovate.** What I found (read-only): - **`gitea-actions`** isn't a real account. It's Gitea's built-in identity for Actions: it shows as the actor on things a workflow does with its automatic job token. It can't sign in or hold a personal access token, and Renovate needs one. - **`gitea`** isn't a Gitea user either. A user search finds only `gitea_admin`. The name matches the mailer login in the Gitea role (`[mailer] USER: gitea`), so it's probably the directory or mail account Gitea sends email with. Using it for Renovate would give one credential a second purpose, which is what I5 (#47) is splitting up. A Renovate token also ends up in an Actions secret, so if it leaked, the mail account would leak with it. **Recommendation:** a local Gitea user such as `renovate-bot`: - Not an admin, and not a member of any team with admin rights. - Added as a **collaborator with Write** only on the repos Renovate should touch. At first that's `DevOps/www` and `DevOps/ansible-role-gitea`. Write lets it push branches and open PRs. Branch protection from G11 (#59) keeps it from merging on its own. - One personal access token with the scopes `write:repository`, `write:issue` (for the dependency dashboard issue) and `read:user`, stored as a repo-level Actions secret `RENOVATE_TOKEN` in whichever repo runs the schedule. - Optionally a read-only GitHub token as `RENOVATE_GITHUB_COM_TOKEN`, so lookups of GitHub-hosted releases don't hit anonymous rate limits. **No rush.** P7 depends on P5 (#65) and G11 (#59), and neither is done yet. When those are in place I'll write the config with a cap of two open PRs and ask for the account then. `needs-eric` stays for the account. — eom-cicd-roadmap
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#67