randy
4c95927231
The runner's label-to-image mapping got repointed at Gitea's own official runner image (docker.gitea.com/runner-images:ubuntu-latest, has Node out of the box) — the earlier opensuse/leap:16.0 mapping for brick-build specifically was what broke check/renovate on 2026-09-12, not brick-build the label itself. Back to pinning both to this machine specifically instead of whichever runner answers to the shared ubuntu-latest label.
33 lines
960 B
YAML
33 lines
960 B
YAML
name: Renovate
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
schedule:
|
|
# Gitea extends standard cron syntax with an optional "TZ=" prefix.
|
|
- cron: "TZ=Europe/Bratislava 0 6 * * 1"
|
|
|
|
jobs:
|
|
renovate:
|
|
# Same reasoning as check's runs-on in ci.yml: brick-build's job
|
|
# container now has Node (repointed at Gitea's own official runner
|
|
# image), which setup-node/npm below need.
|
|
runs-on: brick-build
|
|
steps:
|
|
- name: Setup Node
|
|
uses: actions/setup-node@v4
|
|
with:
|
|
node-version: "22"
|
|
|
|
- name: Install Renovate
|
|
run: npm install -g renovate
|
|
|
|
- name: Run Renovate
|
|
run: renovate
|
|
env:
|
|
RENOVATE_PLATFORM: gitea
|
|
RENOVATE_ENDPOINT: "${{ gitea.server_url }}/api/v1/"
|
|
RENOVATE_TOKEN: ${{ secrets.RENOVATE_TOKEN }}
|
|
RENOVATE_REPOSITORIES: "${{ gitea.repository }}"
|
|
RENOVATE_ONBOARDING: "false"
|
|
GITHUB_COM_TOKEN: ${{ secrets.GITHUB_COM_TOKEN }}
|