fix(renovate): move global-only `gitUrl` option out of repo config #12

Closed

forgejo-actions wants to merge 1 commit from fix/renovate-giturl-global-option into master

forgejo-actions commented

2026-07-01 06:13:43 +00:00

Summary

Fixes the Renovate config warning reported on the Dependency Dashboard (#11):

⚠️ WARN: Found renovate config warnings

Root cause

Reproduced locally by running renovate --dry-run=full (v43.249.5, the same version the runner uses) against this repo. The actual warning is:

The "gitUrl" option is a global option reserved only for Renovate's global configuration and cannot be configured within a repository's config file.

gitUrl is a global / self-hosted option — it lives on Renovate's self-hosted configuration docs page, not the per-repo configuration page. Placing "gitUrl": "endpoint" in the repository's renovate.json is invalid, and Renovate reports it as a config warning on every run — which is exactly what surfaced on the dashboard.

Fix

renovate.json — removed the invalid "gitUrl": "endpoint" entry.
.forgejo/workflows/renovate.yml — injected gitUrl where it belongs: as the global RENOVATE_GIT_URL=endpoint env var on the Run Renovate step (consistent with the other RENOVATE_* global options already passed there). The endpoint value (clone over the configured HTTP API endpoint instead of SSH) is preserved.

Verification

Ran renovate 43.249.5 --dry-run against the repo:

Before: WARN: Found renovate config warnings → gitUrl global-option error.
After: no config warnings, renovate-config-validator passes, the resolved global config still contains "gitUrl": "endpoint" (via the env var), and the Forgejo workflow files are still detected/scanned.

Reference: https://docs.renovatebot.com/modules/platform/forgejo/

Closes #11

## Summary Fixes the Renovate config warning reported on the [Dependency Dashboard (#11)](https://forge.l3x.in/alex/pi-shared/issues/11): > ⚠️ WARN: Found renovate config warnings ### Root cause Reproduced locally by running `renovate --dry-run=full` (v43.249.5, the same version the runner uses) against this repo. The actual warning is: > The **"gitUrl"** option is a global option reserved only for Renovate's global configuration and cannot be configured within a repository's config file. [`gitUrl`](https://docs.renovatebot.com/self-hosted-configuration/) is a **global / self-hosted** option — it lives on Renovate's *self-hosted configuration* docs page, not the per-repo configuration page. Placing `"gitUrl": "endpoint"` in the repository's `renovate.json` is invalid, and Renovate reports it as a config warning on every run — which is exactly what surfaced on the dashboard. ### Fix 1. **`renovate.json`** — removed the invalid `"gitUrl": "endpoint"` entry. 2. **`.forgejo/workflows/renovate.yml`** — injected `gitUrl` where it belongs: as the global `RENOVATE_GIT_URL=endpoint` env var on the `Run Renovate` step (consistent with the other `RENOVATE_*` global options already passed there). The `endpoint` value (clone over the configured HTTP API endpoint instead of SSH) is preserved. ### Verification Ran `renovate 43.249.5 --dry-run` against the repo: - **Before:** `WARN: Found renovate config warnings` → `gitUrl` global-option error. - **After:** no config warnings, `renovate-config-validator` passes, the resolved global config still contains `"gitUrl": "endpoint"` (via the env var), and the Forgejo workflow files are still detected/scanned. Reference: https://docs.renovatebot.com/modules/platform/forgejo/ Closes #11

forgejo-actions added 1 commit

2026-07-01 06:13:43 +00:00

fix(renovate): move global-only gitUrl option out of repo config ab46c14b8e

The `gitUrl` option is a global/self-hosted-only setting and cannot be
placed in a repository's renovate.json. Renovate flagged it as a config
warning ("Found renovate config warnings") on every run.

- renovate.json: remove the invalid `"gitUrl": "endpoint"` entry
- renovate.yml: supply it globally as `RENOVATE_GIT_URL=endpoint`

Verified with renovate 43.249.5 --dry-run: warning gone, validator passes,
gitUrl=endpoint still resolved globally, forgejo workflows still scanned.

Fixes #11

forgejo-actions referenced this pull request

2026-07-01 06:13:59 +00:00

Dependency Dashboard #11