Two follow-ups to the initial Renovate setup (PR #18), needed before the first run:
Secret name — Gitea reserves the GITHUB_ secret-name prefix (same rule as GitHub Actions), so GITHUB_COM_TOKEN was rejected (HTTP 400). Renamed to GH_COM_TOKEN (mapped to RENOVATE_GITHUB_COM_TOKEN in the workflow). The secret is already stored under the new name, and the PAT is verified working (authenticated 5000/hr limit + public release-note read).
Image pin — bump renovate/renovate:41 → :43 (41 was already stale; current major is 43.x).
RENOVATE_TOKEN (bot PAT) + GH_COM_TOKEN (github.com PAT) secrets are set; branch protection on main requires the Build & test (.NET) check. After this merges I'll dry-run, then do a live run.
refs server-management#484
Two follow-ups to the initial Renovate setup (PR #18), needed before the first run:
- **Secret name** — Gitea reserves the `GITHUB_` secret-name prefix (same rule as GitHub Actions), so `GITHUB_COM_TOKEN` was rejected (HTTP 400). Renamed to **`GH_COM_TOKEN`** (mapped to `RENOVATE_GITHUB_COM_TOKEN` in the workflow). The secret is already stored under the new name, and the PAT is verified working (authenticated 5000/hr limit + public release-note read).
- **Image pin** — bump `renovate/renovate:41` → **`:43`** (41 was already stale; current major is 43.x).
`RENOVATE_TOKEN` (bot PAT) + `GH_COM_TOKEN` (github.com PAT) secrets are set; branch protection on `main` requires the `Build & test (.NET)` check. After this merges I'll dry-run, then do a live run.
refs server-management#484
Two follow-ups to the initial Renovate setup (merged in PR #18):
- Gitea reserves the GITHUB_ secret-name prefix (same as GitHub Actions), so the
GITHUB_COM_TOKEN secret was rejected (HTTP 400). Rename to GH_COM_TOKEN and map
it to RENOVATE_GITHUB_COM_TOKEN in the workflow.
- Pin renovate/renovate:43 (current major; 41 was already stale — latest is 43.x).
refs server-management#484
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
timothy
merged commit 350ca3b4b6 into main2026-06-27 01:48:30 +02: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.
Two follow-ups to the initial Renovate setup (PR #18), needed before the first run:
GITHUB_secret-name prefix (same rule as GitHub Actions), soGITHUB_COM_TOKENwas rejected (HTTP 400). Renamed toGH_COM_TOKEN(mapped toRENOVATE_GITHUB_COM_TOKENin the workflow). The secret is already stored under the new name, and the PAT is verified working (authenticated 5000/hr limit + public release-note read).renovate/renovate:41→:43(41 was already stale; current major is 43.x).RENOVATE_TOKEN(bot PAT) +GH_COM_TOKEN(github.com PAT) secrets are set; branch protection onmainrequires theBuild & test (.NET)check. After this merges I'll dry-run, then do a live run.refs server-management#484
timothy referenced this pull request2026-07-11 11:40:25 +02:00