release workflow (pytest-dev/pytest-testinfra)

The release workflow from pytest-dev/pytest-testinfra, explained and optimized by Latchkey.

What it does

This is the release workflow from the pytest-dev/pytest-testinfra 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:
    name: Publish to PyPI registry
    environment:
      name: pypi
      url: https://pypi.org/p/pytest-testinfra
    runs-on: ubuntu-22.04
    permissions:
      id-token: write
    env:
      FORCE_COLOR: 1
      PY_COLORS: 1
    steps:
    - uses: actions/checkout@v6
    - name: Switch to using Python 3.11 by default
      uses: actions/setup-python@v6
      with:
        python-version: "3.11"
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install tox
    - name: Build dists
      run: |
        tox -e packaging
    - name: Publish to pypi.org
      uses: pypa/gh-action-pypi-publish@release/v1

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: release
 
on:
  release:
    types: [published]
 
jobs:
  pypi:
    timeout-minutes: 30
    name: Publish to PyPI registry
    environment:
      name: pypi
      url: https://pypi.org/p/pytest-testinfra
    runs-on: latchkey-small
    permissions:
      id-token: write
    env:
      FORCE_COLOR: 1
      PY_COLORS: 1
    steps:
    - uses: actions/checkout@v6
    - name: Switch to using Python 3.11 by default
      uses: actions/setup-python@v6
      with:
        cache: 'pip'
        python-version: "3.11"
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install tox
    - name: Build dists
      run: |
        tox -e packaging
    - name: Publish to pypi.org
      uses: pypa/gh-action-pypi-publish@release/v1
 

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.

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 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