Compare commits

..
1 Commits
Author SHA1 Message Date
Renovate Bot 397e318a46 chore(deps): update https://git.keligrubb.com/actions/setup-node action to v7
renovate/stability-days Updates have met minimum release age requirement
2026-07-17 03:01:47 +00:00
2 changed files with 4 additions and 21 deletions
+3 -11
View File
@@ -7,19 +7,18 @@ This repo runs [Renovate](https://docs.renovatebot.com/) via **Gitea Actions**,
- **Gitea Actions** runs a single job from `.gitea/workflows/renovate.yml` on a **cron schedule** and on **manual dispatch**.
- The job uses the official `renovatebot/github-action` and reads config from **renovate.json** in this repo.
- Renovate processes every non-mirror Gitea repo the bot token can access (push/pull, PRs enabled), opening and updating PRs. Minor and patch updates are grouped into one PR per repo; major updates use separate PRs.
- Dependencies with known OSV vulnerabilities get their own PRs labeled `security`. They still wait out `minimumReleaseAge` like everything else, so a poisoned release can't land instantly.
## Setup
### 1. Gitea Actions workflow & schedule
The workflow lives in `.gitea/workflows/renovate.yml` and currently runs every hour:
The workflow lives in `.gitea/workflows/renovate.yml` and currently runs every 6 hours:
```yaml
on:
workflow_dispatch:
schedule:
- cron: "0 * * * *"
- cron: "0 */6 * * *"
```
To change the schedule (e.g. daily or weekly), edit the cron expression there and push a commit.
@@ -44,16 +43,9 @@ Create a dedicated Renovate bot user in Gitea (or your IdP) so PRs and commits a
3. Copy the token (shown only once) and store it as the `RENOVATE_TOKEN` secret for this repo (or org) in Gitea Actions.
4. In **renovate.json**, set `gitAuthor` to match the bot (e.g. `"Renovate Bot <renovate-bot@your-domain>"`).
### 4. Labels
Create these labels on the repos (or org-wide) so Renovate can apply them:
- `dependencies` — all update PRs
- `security` — vulnerability-driven PRs
## Configuration
Renovate is configured in **renovate.json**. It sets the platform, autodiscovery, grouping (`group:allNonMajor`), best-practices presets, OSV vulnerability alerts, abandoned-package reporting, PR rate limits, and disables the Dependency Dashboard via the `:disableDependencyDashboard` preset (so it stays off even if other presets enable it). Token and endpoint are provided only via environment (secrets).
Renovate is configured in **renovate.json**. It sets the platform, autodiscovery, grouping (`group:allNonMajor`), best-practices presets, and disables the Dependency Dashboard via the `:disableDependencyDashboard` preset (so it stays off even if other presets enable it). Token and endpoint are provided only via environment (secrets).
**Target repos:** If a repo has its own **renovate.json**, it is merged on top of this global config. A repo that sets its own `extends` (e.g. `"extends": ["config:recommended"]`) can effectively replace the global presets, lose grouping, or re-enable the dashboard. To keep bundled PRs and no dashboard, either omit per-repo configs or ensure they do not override `extends` / dashboard settings.
+1 -10
View File
@@ -3,8 +3,7 @@
"config:recommended",
":configMigration",
"group:allNonMajor",
":disableDependencyDashboard",
"abandonments:recommended"
":disableDependencyDashboard"
],
"gitAuthor": "Renovate Bot <renovate@keligrubb.com>",
"semanticCommits": "enabled",
@@ -13,14 +12,6 @@
"prBodyTemplate": "{{{header}}}{{{table}}}{{{warnings}}}{{{notes}}}{{{changelogs}}}{{{controls}}}",
"minimumReleaseAge": "3 days",
"rangeStrategy": "auto",
"labels": ["dependencies"],
"osvVulnerabilityAlerts": true,
"vulnerabilityAlerts": {
"enabled": true,
"labels": ["security", "dependencies"]
},
"prConcurrentLimit": 5,
"prHourlyLimit": 5,
"dockerfile": {
"digest": { "enabled": false }
},