Publish on PyPI workflow (scikit-rf/scikit-rf)
The Publish on PyPI workflow from scikit-rf/scikit-rf, 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 Publish on PyPI workflow from the scikit-rf/scikit-rf repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
# This workflows will upload a Python Package using uv when a release is created
# reference:
# https://github.com/astral-sh/trusted-publishing-examples/blob/main/.github/workflows/release.yml
name: Publish on PyPI
on:
release:
types:
- published
jobs:
build_and_deploy:
runs-on: ubuntu-latest
permissions:
# IMPORTANT: this permission is mandatory for trusted publishing
id-token: write
steps:
- name: Checkout Project
uses: actions/checkout@v7
- name: Install uv
uses: astral-sh/setup-uv@v8.2.0
- name: Set Up Python
run: uv python install
- name: Build Package
run: uv build
- name: Publish to PyPi
run: uv publish --trusted-publishing always
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
# This workflows will upload a Python Package using uv when a release is created # reference: # https://github.com/astral-sh/trusted-publishing-examples/blob/main/.github/workflows/release.yml name: Publish on PyPI on: release: types: - published jobs: build_and_deploy: timeout-minutes: 30 runs-on: latchkey-small permissions: # IMPORTANT: this permission is mandatory for trusted publishing id-token: write steps: - name: Checkout Project uses: actions/checkout@v7 - name: Install uv uses: astral-sh/setup-uv@v8.2.0 - name: Set Up Python run: uv python install - name: Build Package run: uv build - name: Publish to PyPi run: uv publish --trusted-publishing always
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.