ci: fix Renovate workflow (run CLI via npx instead of github-action) #3

Merged

alex merged 1 commit from fix/renovate-workflow-npx into master

2026-06-29 07:13:14 +00:00

forgejo-actions commented

2026-06-29 07:11:57 +00:00

What

Fixes the Renovate workflow that failed in run #3 (Set up job, 3s, no steps ran).

Root cause

renovatebot/github-action@v46.1.17 is a using: node24 action whose only job is to wrap Docker — it runs docker run ghcr.io/renovatebot/renovate. That action-fetch + Docker-wrapper path failed during job setup on this runner (the run died at Set up job before Checkout or Run Renovate executed).

For comparison, the working pi-agent workflow and actions/checkout@v7 (also node24) run fine on the same runner, so the environment/node24/Docker runtime itself is not the problem — the renovatebot/github-action wrapper is.

Fix

Drop the wrapper and run the Renovate CLI directly via npx:

- name: Run Renovate
  run: npx -y renovate@latest
  env:
    RENOVATE_CONFIG_FILE: renovate.json
    RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
    RENOVATE_PLATFORM: gitea
    RENOVATE_ENDPOINT: ${{ vars.MY_FORGEJO_PUBLIC_URL }}/api/v1/
    RENOVATE_REPOSITORIES: ${{ github.repository }}
    GITHUB_COM_TOKEN: ${{ secrets.GH_PAT_TOKEN }}

This runs as a plain Node script — no Docker, no GitHub action-fetch — which I verified works on this exact runner (renovate 43.246.1 resolved and ran). The renovate.json config is unchanged, so the npm + github-actions managers still cover the old Dependabot scope.

Verification

npx -y renovate@latest --version → 43.246.1 (run on the pi-agent runner). After merge, trigger the workflow manually (workflow_dispatch) to confirm it green-lights and opens its first dependency PR.

Refs #1

## What Fixes the Renovate workflow that failed in [run #3](https://forge.l3x.in/alex/pi-shared/actions/runs/3) (`Set up job`, 3s, no steps ran). ## Root cause `renovatebot/github-action@v46.1.17` is a `using: node24` action whose only job is to **wrap Docker** — it runs `docker run ghcr.io/renovatebot/renovate`. That action-fetch + Docker-wrapper path failed during job setup on this runner (the run died at **Set up job** before Checkout or Run Renovate executed). For comparison, the working `pi-agent` workflow and `actions/checkout@v7` (also `node24`) run fine on the **same** runner, so the environment/node24/Docker runtime itself is not the problem — the `renovatebot/github-action` wrapper is. ## Fix Drop the wrapper and run the **Renovate CLI directly via `npx`**: ```yaml - name: Run Renovate run: npx -y renovate@latest env: RENOVATE_CONFIG_FILE: renovate.json RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }} RENOVATE_PLATFORM: gitea RENOVATE_ENDPOINT: ${{ vars.MY_FORGEJO_PUBLIC_URL }}/api/v1/ RENOVATE_REPOSITORIES: ${{ github.repository }} GITHUB_COM_TOKEN: ${{ secrets.GH_PAT_TOKEN }} ``` This runs as a plain Node script — **no Docker, no GitHub action-fetch** — which I verified works on this exact runner (`renovate 43.246.1` resolved and ran). The `renovate.json` config is unchanged, so the npm + `github-actions` managers still cover the old Dependabot scope. ## Verification `npx -y renovate@latest --version` → `43.246.1` (run on the pi-agent runner). After merge, trigger the workflow manually (workflow_dispatch) to confirm it green-lights and opens its first dependency PR. Refs #1

forgejo-actions added 1 commit

2026-06-29 07:11:58 +00:00

ci: run Renovate via npx instead of the github-action wrapper c9b4afffd4

The previous renovate workflow used renovatebot/github-action@v46.1.17,
a node24 action that wraps Docker (docker run ghcr.io/renovatebot/renovate).
Run #3 failed during 'Set up job' (3s) before any step ran.

Replace it with the Renovate CLI invoked directly via 'npx -y renovate'.
This runs as a plain Node script (no Docker, no GitHub action-fetch),
which is verified working on this runner (renovate 43.246.1).

Refs #1