Dependency Dashboard

alex commented

2026-07-01 05:55:52 +00:00

Owner

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

Renovate tried to run on this repository, but found these problems.

WARN: Found renovate config warnings

This repository currently has no open or pending branches.

Detected dependencies

bun

package.json

@earendil-works/pi-coding-agent ^0.80.2

github-actions

.forgejo/workflows/pi.yml

actions/checkout v7

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Repository problems Renovate tried to run on this repository, but found these problems. - WARN: Found renovate config warnings This repository currently has no open or pending branches. ## Detected dependencies <details><summary>bun</summary> <blockquote> <details><summary>package.json</summary> - `@earendil-works/pi-coding-agent ^0.80.2` </details> </blockquote> </details> <details><summary>github-actions</summary> <blockquote> <details><summary>.forgejo/workflows/pi.yml</summary> - `actions/checkout v7` </details> </blockquote> </details>

alex commented

2026-07-01 06:00:53 +00:00

Author

Owner

/pi check https://forge.l3x.in/alex/pi-shared/actions/runs/16/jobs/0/attempt/1 and use https://docs.renovatebot.com/modules/platform/forgejo/ as reference, fix the problems in a new PR

forgejo-actions referenced this issue from a commit

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

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

forgejo-actions referenced this issue from a pull request that will close it,

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

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

forgejo-actions commented

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

I'll investigate the repository structure and the Renovate configuration to understand the problems.Now let me look at the Renovate config and other relevant files.Let me try to access the Forgejo run logs and check the Renovate documentation/schema for config warnings.I can't access the Forgejo instance directly. Let me analyze the Renovate schema to identify the config warnings.The default github-actions manager already covers .forgejo/workflows/. Let me run Renovate's config validator against the actual config to see exactly what warnings it reports.renovate-config-validator is bundled inside the renovate package. Let me invoke it directly.The config validator passes (it only checks hard errors). The runtime "config warnings" surface during an actual run. Let me consult the Renovate Forgejo platform docs that the user referenced, as it likely documents the specific gotchas.The docs match Renovate 43.249.5 (same as installed). The validator only catches hard errors, not runtime "config warnings". Let me run Renovate against this local repo in dry-run mode to reproduce the exact warnings.Reproduced it. The warning is about the github-actions config block. Let me get the full warning text.Found the actual warning. It 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.

The gitUrl: "endpoint" in renovate.json is the culprit — gitUrl is a global-only option and must not live in the repo config file. Let me confirm this in the schema and find the correct env-var name to relocate it.Let me confirm the gitUrl option details and the correct environment-variable form from Renovate's configuration docs.Confirmed: gitUrl is a self-hosted/global-only option (it appears on the self-hosted-configuration page, not repo config). The env-var form is RENOVATE_GIT_URL. Let me verify that removing it from renovate.json and setting RENOVATE_GIT_URL=endpoint clears the warning.Now I understand the mechanism fully: RENOVATE_CONFIG_FILE is the global config, while renovate.json in the repo is the repo config (which still has gitUrl). The RENOVATE_GIT_URL=endpoint env var IS being recognized (it shows "gitUrl": "endpoint" in the resolved global config), but the repo file still carries the invalid option.

The fix is clear: remove gitUrl from the repo renovate.json and relocate it to the global config via RENOVATE_GIT_URL in the workflow. Let me apply both edits.Now let me verify the warning is gone by running Renovate against the actual (now-fixed) repo config, with gitUrl supplied globally via the env var.The config warning is gone (grep returned no matches). Let me confirm the run still completes cleanly and that gitUrl=endpoint is correctly resolved from the global env, then review the final workflow file.Everything is verified: gitUrl: endpoint resolves correctly from the global env, no config warning, and the run completes successfully. Let me review the final diff and create the PR.The PR tool targets GitHub but this repo is on Forgejo. Let me check the remote and push the branch, then create the PR via the Forgejo API.Token works. Let me create a branch, commit the fix, push, and open the PR via the Forgejo API.Branch pushed. Now let me create the PR via the Forgejo API.PR created: #12

Summary

I couldn't reach the Forgejo run page directly (CI runner has no external network), so I reproduced the failure locally by running the same Renovate version the runner uses (43.249.5) in --dry-run=full against the repo. That surfaced the exact config warning behind the dashboard's "⚠️ WARN: Found renovate config warnings":

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

Root cause

gitUrl is a global / self-hosted-only option (it's documented on Renovate's self-hosted configuration page, not the per-repo page). The repo's renovate.json had "gitUrl": "endpoint", which is invalid there and gets flagged as a config warning on every run.

Fix (PR #12)

renovate.json — removed the invalid "gitUrl": "endpoint" entry.
.forgejo/workflows/renovate.yml — moved it to where it belongs: the global RENOVATE_GIT_URL=endpoint env var on the Run Renovate step (alongside the other RENOVATE_* globals). The endpoint behavior (clone over the HTTP API endpoint instead of SSH) is preserved.

Verified

renovate-config-validator passes.
Re-ran renovate --dry-run after the fix: no config warnings, the resolved global config still contains "gitUrl": "endpoint" (now from the env var), and the Forgejo workflow files are still detected/scanned.

Closes #11.

I'll investigate the repository structure and the Renovate configuration to understand the problems.Now let me look at the Renovate config and other relevant files.Let me try to access the Forgejo run logs and check the Renovate documentation/schema for config warnings.I can't access the Forgejo instance directly. Let me analyze the Renovate schema to identify the config warnings.The default github-actions manager already covers `.forgejo/workflows/`. Let me run Renovate's config validator against the actual config to see exactly what warnings it reports.`renovate-config-validator` is bundled inside the `renovate` package. Let me invoke it directly.The config validator passes (it only checks hard errors). The runtime "config warnings" surface during an actual run. Let me consult the Renovate Forgejo platform docs that the user referenced, as it likely documents the specific gotchas.The docs match Renovate 43.249.5 (same as installed). The validator only catches hard errors, not runtime "config warnings". Let me run Renovate against this local repo in dry-run mode to reproduce the exact warnings.Reproduced it. The warning is about the `github-actions` config block. Let me get the full warning text.**Found the actual warning.** It 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. The `gitUrl: "endpoint"` in `renovate.json` is the culprit — `gitUrl` is a **global-only** option and must not live in the repo config file. Let me confirm this in the schema and find the correct env-var name to relocate it.Let me confirm the `gitUrl` option details and the correct environment-variable form from Renovate's configuration docs.Confirmed: `gitUrl` is a **self-hosted/global-only** option (it appears on the self-hosted-configuration page, not repo config). The env-var form is `RENOVATE_GIT_URL`. Let me verify that removing it from `renovate.json` and setting `RENOVATE_GIT_URL=endpoint` clears the warning.Now I understand the mechanism fully: `RENOVATE_CONFIG_FILE` is the *global* config, while `renovate.json` in the repo is the *repo* config (which still has `gitUrl`). The `RENOVATE_GIT_URL=endpoint` env var IS being recognized (it shows `"gitUrl": "endpoint"` in the resolved global config), but the repo file still carries the invalid option. The fix is clear: remove `gitUrl` from the repo `renovate.json` and relocate it to the global config via `RENOVATE_GIT_URL` in the workflow. Let me apply both edits.Now let me verify the warning is gone by running Renovate against the actual (now-fixed) repo config, with `gitUrl` supplied globally via the env var.The config warning is gone (grep returned no matches). Let me confirm the run still completes cleanly and that `gitUrl=endpoint` is correctly resolved from the global env, then review the final workflow file.Everything is verified: `gitUrl: endpoint` resolves correctly from the global env, no config warning, and the run completes successfully. Let me review the final diff and create the PR.The PR tool targets GitHub but this repo is on Forgejo. Let me check the remote and push the branch, then create the PR via the Forgejo API.Token works. Let me create a branch, commit the fix, push, and open the PR via the Forgejo API.Branch pushed. Now let me create the PR via the Forgejo API.PR created: **https://forge.l3x.in/alex/pi-shared/pulls/12** ## Summary I couldn't reach the Forgejo run page directly (CI runner has no external network), so I reproduced the failure locally by running the **same Renovate version the runner uses (43.249.5)** in `--dry-run=full` against the repo. That surfaced the exact config warning behind the dashboard's "⚠️ WARN: Found renovate config warnings": > The **"gitUrl"** option is a global option reserved only for Renovate's global configuration and cannot be configured within a repository's config file. ### Root cause [`gitUrl`](https://docs.renovatebot.com/self-hosted-configuration/) is a **global / self-hosted-only** option (it's documented on Renovate's *self-hosted configuration* page, not the per-repo page). The repo's `renovate.json` had `"gitUrl": "endpoint"`, which is invalid there and gets flagged as a config warning on every run. ### Fix (PR #12) 1. **`renovate.json`** — removed the invalid `"gitUrl": "endpoint"` entry. 2. **`.forgejo/workflows/renovate.yml`** — moved it to where it belongs: the global `RENOVATE_GIT_URL=endpoint` env var on the `Run Renovate` step (alongside the other `RENOVATE_*` globals). The `endpoint` behavior (clone over the HTTP API endpoint instead of SSH) is preserved. ### Verified - `renovate-config-validator` passes. - Re-ran `renovate --dry-run` after the fix: **no config warnings**, the resolved global config still contains `"gitUrl": "endpoint"` (now from the env var), and the Forgejo workflow files are still detected/scanned. Closes #11. --- [View action run](https://forge.l3x.in/alex/pi-shared/actions/runs/18) | Model: zai/glm-5.2 (thinking: xhigh) | Time: 13m 6s | Tokens: 457.9K | Pi SDK v0.80.3 | Action v2.25.0-develop (develop @ 0e171ae)

alex commented

2026-07-01 06:18:28 +00:00

Author

Owner

Adding forgejo-wide renovate bot, this is stale now

alex closed this issue

2026-07-01 06:18:28 +00:00

Rows
Columns

Dependency Dashboard #11

Repository problems

Detected dependencies

Summary

Root cause

Fix (PR #12)

Verified