Build wheels workflow (coleifer/peewee)

The Build wheels workflow from coleifer/peewee, explained and optimized by Latchkey.

What it does

This is the Build wheels workflow from the coleifer/peewee 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: Build wheels
on:
 push:
   tags:
     - "[0-9]+.[0-9]+.[0-9]+"
     - "[0-9]+.[0-9]+.[0-9]+-**"

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-python@v5
        with:
          python-version: "3.12"

      - name: Install build tools
        run: |
          python -m pip install -U pip
          pip install setuptools build

      - name: Build sdist and wheel
        env:
          NO_SQLITE: 1
        run: |
          python -m build .

      - uses: actions/upload-artifact@v4
        with:
          name: package
          path: dist/peewee*

  publish:
    needs: [build]
    runs-on: ubuntu-latest
    steps:
      - uses: actions/download-artifact@v4
        with:
          name: package
          path: dist
          merge-multiple: true

      - uses: pypa/gh-action-pypi-publish@release/v1
        with:
          user: __token__
          password: ${{ secrets.PYPI_API_TOKEN }}

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: Build wheels
on:
 push:
   tags:
     - "[0-9]+.[0-9]+.[0-9]+"
     - "[0-9]+.[0-9]+.[0-9]+-**"
 
concurrency:
 group: ${{ github.workflow }}-${{ github.ref }}
 cancel-in-progress: true
 
jobs:
  build:
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
 
      - uses: actions/setup-python@v5
        with:
         cache: 'pip'
          python-version: "3.12"
 
      - name: Install build tools
        run: |
          python -m pip install -U pip
          pip install setuptools build
 
      - name: Build sdist and wheel
        env:
          NO_SQLITE: 1
        run: |
          python -m build .
 
      - uses: actions/upload-artifact@v4
        with:
          name: package
          path: dist/peewee*
 
  publish:
    needs: [build]
    runs-on: latchkey-small
    steps:
      - uses: actions/download-artifact@v4
        with:
          name: package
          path: dist
          merge-multiple: true
 
      - uses: pypa/gh-action-pypi-publish@release/v1
        with:
          user: __token__
          password: ${{ secrets.PYPI_API_TOKEN }}
 

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.
• Cancel superseded runs when a branch or PR gets a newer push.
• Cache dependency installs on the setup step so they are served from cache.

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.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow