chore(ci): set up Renovate dependency automation #11

Merged
julien merged 1 commits from chore/ci/renovate-setup into main 2026-05-04 17:37:14 +02:00

1 Commits

Author SHA1 Message Date
Julien Gautier c55c549b81 chore(ci): set up Renovate dependency automation
CI / commits (pull_request) Successful in 1m36s
CI / check (pull_request) Successful in 1m40s
CI / a11y (pull_request) Successful in 40s
CI / perf (pull_request) Successful in 1m54s
CI / scan (pull_request) Failing after 3m39s
Renovate runs as a daily Gitea Actions cron (03:00 UTC, on
self-hosted runners) and opens PRs against main for dependency
updates. Picked daily-at-3am specifically so Monday's run sits
inside Renovate's default `lockFileMaintenance.schedule` ("before
4am on Monday") and triggers the weekly lockfile refresh in passing.

The workflow only handles invocation + Gitea-platform plumbing.
Bot behaviour (groupings, labels, Conventional Commits, OSV.dev
vulnerability source) lives in /renovate.json so it can evolve
without redeploying the workflow.

Groups defined: Angular, Nx, NestJS, Prisma (incl. nestjs-prisma),
Vitest, TypeScript tooling, ESLint, SWC, Tailwind. Standalone
packages get individual PRs.

Bot identity: a dedicated `apf-portal-bot` Gitea user authenticates
with a PAT stored as the RENOVATE_TOKEN repo secret. The full
onboarding procedure (user creation, scopes, secret) is documented
in docs/development.md → "Dependency updates (Renovate)".

The roadmap entry for Renovate is removed from §8 since the section
now exists.
2026-05-04 16:39:33 +02:00