Release workflow (devon-mar/netbox-kea)
The Release workflow from devon-mar/netbox-kea, 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 Release workflow from the devon-mar/netbox-kea 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: Release
"on":
release:
types:
- published
jobs:
pypi-publish:
runs-on: ubuntu-latest
permissions:
# https://docs.pypi.org/trusted-publishers/
id-token: write
steps:
- uses: actions/checkout@v7
- name: Install uv
uses: astral-sh/setup-uv@v7
with:
enable-cache: true
- run: uv build
- run: uv publish
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
--- name: Release "on": release: types: - published jobs: pypi-publish: timeout-minutes: 30 runs-on: latchkey-small permissions: # https://docs.pypi.org/trusted-publishers/ id-token: write steps: - uses: actions/checkout@v7 - name: Install uv uses: astral-sh/setup-uv@v7 with: enable-cache: true - run: uv build - run: uv publish
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.