alex/pi-shared

Watch

Fork 0

Dependency Dashboard #14

New issue

Open

opened 2026-07-01 11:15:26 +00:00 by alex · 2 comments

alex commented

2026-07-01 11:15:26 +00:00

Owner

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

Awaiting Schedule

The following updates are awaiting their schedule. To get an update now, click on a checkbox below.

chore(deps): lock file maintenance

Detected Dependencies

bun (1)

package.json (1)

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

github-actions (1)

.forgejo/workflows/pi.yml

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Awaiting Schedule The following updates are awaiting their schedule. To get an update now, click on a checkbox below. - [ ] chore(deps): lock file maintenance ## Detected Dependencies <details><summary>bun (1)</summary> <blockquote> <details><summary>package.json (1)</summary> - `@earendil-works/pi-coding-agent ^0.82.0` </details> </blockquote> </details> <details><summary>github-actions (1)</summary> <blockquote> <details><summary>.forgejo/workflows/pi.yml</summary> </details> </blockquote> </details>

alex added the

dependencies

label

2026-07-01 12:38:56 +00:00

alex commented

2026-07-01 12:39:09 +00:00

Author

Owner

/pi can you fix the warning? if so create a new PR

forgejo-actions referenced this issue

2026-07-01 12:41:05 +00:00

ci(renovate): ignore internal Forgejo workflow reference alex/.profile #15

forgejo-actions commented

2026-07-01 12:41:13 +00:00

I can see the issue. This repository is hosted on Forgejo (http://forgejo:3000/alex/pi-shared), but Renovate is trying to look up the reusable workflow reference alex/.profile as a GitHub package (using the github-digest datasource). Since alex/.profile lives on Forgejo and not GitHub, the lookup fails with "no-result".

The fix is to tell Renovate to ignore this internal workflow reference via the existing renovate.json.Now let me create the PR.The automated PR tool failed (likely because this is a Forgejo instance, not GitHub). Let me create the branch and PR manually via the Forgejo API.Branch pushed. Now let me create the PR via the Forgejo API.Yes, I was able to fix the warning and created PR #15: #15

What was the problem

.forgejo/workflows/pi.yml references a reusable workflow from alex/.profile:

uses: alex/.profile/.forgejo/workflows/pi.yml@master

That repo lives on Forgejo (http://forgejo:3000/alex/.profile), but Renovate's github-actions manager resolves reusable-workflow references against GitHub (github-digest datasource). Since alex/.profile isn't a GitHub repo, the lookup fails with no-result.

The fix

Added a packageRules entry to renovate.json that disables the github-actions manager for the alex/.profile package:

"packageRules": [
  {
    "matchManagers": ["github-actions"],
    "matchPackageNames": ["alex/.profile"],
    "enabled": false
  }
]

This makes Renovate stop trying to resolve that internal Forgejo reference, clearing the warning. The workflow file itself is left untouched, so the reusable workflow still works as before.

I can see the issue. This repository is hosted on Forgejo (`http://forgejo:3000/alex/pi-shared`), but Renovate is trying to look up the reusable workflow reference `alex/.profile` as a GitHub package (using the `github-digest` datasource). Since `alex/.profile` lives on Forgejo and not GitHub, the lookup fails with "no-result". The fix is to tell Renovate to ignore this internal workflow reference via the existing `renovate.json`.Now let me create the PR.The automated PR tool failed (likely because this is a Forgejo instance, not GitHub). Let me create the branch and PR manually via the Forgejo API.Branch pushed. Now let me create the PR via the Forgejo API.Yes, I was able to fix the warning and created **PR #15**: https://forge.l3x.in/alex/pi-shared/pulls/15 ### What was the problem `.forgejo/workflows/pi.yml` references a reusable workflow from `alex/.profile`: ```yaml uses: alex/.profile/.forgejo/workflows/pi.yml@master ``` That repo lives on **Forgejo** (`http://forgejo:3000/alex/.profile`), but Renovate's `github-actions` manager resolves reusable-workflow references against **GitHub** (`github-digest` datasource). Since `alex/.profile` isn't a GitHub repo, the lookup fails with `no-result`. ### The fix Added a `packageRules` entry to `renovate.json` that disables the `github-actions` manager for the `alex/.profile` package: ```json "packageRules": [ { "matchManagers": ["github-actions"], "matchPackageNames": ["alex/.profile"], "enabled": false } ] ``` This makes Renovate stop trying to resolve that internal Forgejo reference, clearing the warning. The workflow file itself is left untouched, so the reusable workflow still works as before. --- [View action run](https://forge.l3x.in/alex/pi-shared/actions/runs/20) | Model: zai/glm-5.2 (thinking: xhigh) | Time: 1m 57s | Tokens: 55.0K | Pi SDK v0.80.3 | Action v2.25.0-develop (develop @ 0e171ae)

alex referenced this issue from a commit

2026-07-01 12:42:20 +00:00

ci(renovate): ignore internal Forgejo workflow reference alex/.profile (#15)

No labels

dependencies

No milestone

No assignees

2 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

alex/pi-shared#14

No description provided.

Rows
Columns