Renovate workflow (okteto/okteto)
The Renovate workflow from okteto/okteto, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Renovate workflow from the okteto/okteto repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: Renovate
on:
workflow_dispatch:
schedule:
# Daily run at 04:00 UTC. Renovate schedules in .github/renovate.json decide what PRs to open/update.
- cron: "0 4 * * *"
concurrency:
group: renovate
cancel-in-progress: false
jobs:
renovate:
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v7
- name: Run Renovate
uses: renovatebot/github-action@v46.1.18
with:
configurationFile: .github/renovate.json
token: ${{ secrets.RENOVATEBOT_GITHUB_TOKEN }}
env:
LOG_LEVEL: debug
RENOVATE_REPOSITORIES: ${{ github.repository }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Renovate on: workflow_dispatch: schedule: # Daily run at 04:00 UTC. Renovate schedules in .github/renovate.json decide what PRs to open/update. - cron: "0 4 * * *" concurrency: group: renovate cancel-in-progress: false jobs: renovate: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout repository uses: actions/checkout@v7 - name: Run Renovate uses: renovatebot/github-action@v46.1.18 with: configurationFile: .github/renovate.json token: ${{ secrets.RENOVATEBOT_GITHUB_TOKEN }} env: LOG_LEVEL: debug RENOVATE_REPOSITORIES: ${{ github.repository }}
What changed
- Run on Latchkey managed runners with one line (
runs-on), which apply the fixes below automatically and self-heal transient failures. This example useslatchkey-small; pick the runner size that fits the job. - Add a job timeout so a hung step cannot burn hours of runner time.
1 third-party action is referenced by a movable tag. Pin it to the commit SHA (Latchkey resolves and applies this automatically) so a repointed tag cannot change what runs.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.