randy
c894706140
brick-build's job container (opensuse/leap:16.0) has no Node.js, and every step in check/renovate (checkout, setup-ruby, setup-node) is a JS-based Action that needs it just to start — both runs since the brick-build switch failed immediately, and deploy never ran because it depends on check passing. ubuntu-latest is shared with "Gitea Runner on Cube" (not pinned to this specific machine), but that's fine: only deploy (a unique label held by just brick's native runner) actually needs to land on a specific box.
32 lines
906 B
YAML
32 lines
906 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 has no Node, which setup-node/npm below need.
|
|
runs-on: ubuntu-latest
|
|
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 }}
|