Publish to PyPI workflow (nolar/kopf)

The Publish to PyPI workflow from nolar/kopf, explained and optimized by Latchkey.

What it does

This is the Publish to PyPI workflow from the nolar/kopf repository, a real project running GitHub Actions. It is shown here with attribution under its MIT license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Publish to PyPI
on:
  release:
    types:
      - published
#  push:
#    tags:
#      - "[0-9]+.[0-9]+*"
  workflow_dispatch: {}

jobs:
  publish:
    name: Build and publish
    runs-on: ubuntu-24.04
    permissions:
      id-token: write  # for trusted publishing
    steps:
      - uses: actions/checkout@v6
      - uses: astral-sh/setup-uv@v7
      - uses: actions/setup-python@v6
        with:
          python-version: "3.14"
      - run: uv build
      - uses: pypa/gh-action-pypi-publish@release/v1
        with:
          skip_existing: true

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Publish to PyPI
on:
  release:
    types:
      - published
#  push:
#    tags:
#      - "[0-9]+.[0-9]+*"
  workflow_dispatch: {}
 
jobs:
  publish:
    timeout-minutes: 30
    name: Build and publish
    runs-on: latchkey-small
    permissions:
      id-token: write  # for trusted publishing
    steps:
      - uses: actions/checkout@v6
      - uses: astral-sh/setup-uv@v7
      - uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: "3.14"
      - run: uv build
      - uses: pypa/gh-action-pypi-publish@release/v1
        with:
          skip_existing: true
 

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 uses latchkey-small; pick the runner size that fits the job.
• Cache dependency installs on the setup step so they are served from cache.
• Add a job timeout so a hung step cannot burn hours of runner time.

2 third-party actions are referenced by a movable tag. Pin them 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.

Actions used in this workflow