Gitea has no hosted Renovate, so the repository runs the official image
from a scheduled Gitea Actions workflow. The platform settings stay in the
workflow environment because Renovate accepts them only in the self-hosted
config, not in renovate.json.
renovate.json keeps the repository config minimal: schema plus
automerge=true, which also covers major updates. The bot account and the
RENOVATE_TOKEN secret are the remaining manual steps.
Gitea has no hosted Renovate, so the repository runs the official image
from a scheduled Gitea Actions workflow. The platform settings stay in the
workflow environment because Renovate accepts them only in the self-hosted
config, not in renovate.json.
renovate.json keeps the repository config minimal: schema plus
automerge=true, which also covers major updates. The bot account and the
RENOVATE_TOKEN secret are the remaining manual steps.
Gitea has no hosted Renovate, so the repository runs the official image
from a scheduled Gitea Actions workflow. The platform settings stay in the
workflow environment because Renovate accepts them only in the self-hosted
config, not in renovate.json.
renovate.json keeps the repository config minimal: schema plus
automerge=true, which also covers major updates. The bot account and the
RENOVATE_TOKEN secret are the remaining manual steps.
build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
build · claude-haiku-5-5
[WARN] renovate.json:3 - "automerge": true applies to every update, including major versions and new transitive dependencies, with no packageRules scoping. The workflow comment says branch protection should gate merges, but that is a manual step this diff does not enforce. Renovate's own test-status wait only covers checks the repo actually runs. Fix: scope automerge to minor/patch and digest updates, e.g. "packageRules": [{"matchUpdateTypes": ["minor", "patch", "digest"], "automerge": true}], and leave majors for manual review. Also add "minimumReleaseAge": "3 days" so freshly published (possibly malicious) versions are not merged immediately.
[WARN] .gitea/workflows/renovate.yml:43 - RENOVATE_TOKEN is exported as an env var to the job, and Renovate runs npm/pnpm installs with lifecycle scripts inside this container, so any dependency's postinstall script can read the token. The token has repo write access and can merge PRs, so this is a credential-exposure path. Fix: disable install scripts for Renovate's own package-manager runs in renovate.json ("ignoreScripts": true), or pin the token to a narrower bot account. If scripts are needed for some packages, allow them explicitly with allowScripts.
[NIT] .gitea/workflows/renovate.yml:35 - The image is pinned by tag only. Pinning by digest (renovate/renovate:44.198.2@sha256:...) prevents a retagged image from changing what runs with the token. This matters more because the job holds a write-scoped secret.
[NIT] .gitea/workflows/renovate.yml:42 - The endpoint is hardcoded. This is fine for this instance, but it should match the Gitea host the token was issued for, so a misconfigured fork cannot send the token elsewhere. No change required if this is intentional.
VERDICT: APPROVE
[0m
> build · claude-haiku-5-5
[0m→ [0mRead .pr-review-diff.patch
> build · claude-haiku-5-5
[WARN] renovate.json:3 - `"automerge": true` applies to every update, including major versions and new transitive dependencies, with no `packageRules` scoping. The workflow comment says branch protection should gate merges, but that is a manual step this diff does not enforce. Renovate's own test-status wait only covers checks the repo actually runs. Fix: scope automerge to minor/patch and digest updates, e.g. `"packageRules": [{"matchUpdateTypes": ["minor", "patch", "digest"], "automerge": true}]`, and leave majors for manual review. Also add `"minimumReleaseAge": "3 days"` so freshly published (possibly malicious) versions are not merged immediately.
[WARN] .gitea/workflows/renovate.yml:43 - `RENOVATE_TOKEN` is exported as an env var to the job, and Renovate runs npm/pnpm installs with lifecycle scripts inside this container, so any dependency's `postinstall` script can read the token. The token has repo write access and can merge PRs, so this is a credential-exposure path. Fix: disable install scripts for Renovate's own package-manager runs in `renovate.json` (`"ignoreScripts": true`), or pin the token to a narrower bot account. If scripts are needed for some packages, allow them explicitly with `allowScripts`.
[NIT] .gitea/workflows/renovate.yml:35 - The image is pinned by tag only. Pinning by digest (`renovate/renovate:44.198.2@sha256:...`) prevents a retagged image from changing what runs with the token. This matters more because the job holds a write-scoped secret.
[NIT] .gitea/workflows/renovate.yml:42 - The endpoint is hardcoded. This is fine for this instance, but it should match the Gitea host the token was issued for, so a misconfigured fork cannot send the token elsewhere. No change required if this is intentional.
VERDICT: APPROVE
Noel
merged commit a129e89aec into main2026-10-30 19:51:33 +00:00
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.
Gitea has no hosted Renovate, so the repository runs the official image
from a scheduled Gitea Actions workflow. The platform settings stay in the
workflow environment because Renovate accepts them only in the self-hosted
config, not in renovate.json.
renovate.json keeps the repository config minimal: schema plus
automerge=true, which also covers major updates. The bot account and the
RENOVATE_TOKEN secret are the remaining manual steps.
[0m
[WARN] .gitea/workflows/renovate.yml:43 -
RENOVATE_TOKENis exported as an env var to the job, and Renovate runs npm/pnpm installs with lifecycle scripts inside this container, so any dependency'spostinstallscript can read the token. The token has repo write access and can merge PRs, so this is a credential-exposure path. Fix: disable install scripts for Renovate's own package-manager runs inrenovate.json("ignoreScripts": true), or pin the token to a narrower bot account. If scripts are needed for some packages, allow them explicitly withallowScripts.[NIT] .gitea/workflows/renovate.yml:35 - The image is pinned by tag only. Pinning by digest (
renovate/renovate:44.198.2@sha256:...) prevents a retagged image from changing what runs with the token. This matters more because the job holds a write-scoped secret.[NIT] .gitea/workflows/renovate.yml:42 - The endpoint is hardcoded. This is fine for this instance, but it should match the Gitea host the token was issued for, so a misconfigured fork cannot send the token elsewhere. No change required if this is intentional.
VERDICT: APPROVE