Upload Python Package workflow (otto-torino/django-baton)

The Upload Python Package workflow from otto-torino/django-baton, explained and optimized by Latchkey.

What it does

This is the Upload Python Package workflow from the otto-torino/django-baton 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: Upload Python Package

on:
  push:
    tags:
      - '*'

permissions:
  contents: read

jobs:
  build:
    name: Build distribution
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v5
    - name: Set up Python
      uses: actions/setup-python@v6
      with:
        python-version: '3.x'
    - name: Build sdist and wheel
      run: |
        python -m pip install --upgrade pip build
        python -m build
    - name: Upload built distributions
      uses: actions/upload-artifact@v7
      with:
        name: dist
        path: dist/

  publish:
    name: Publish to PyPI
    needs: build
    runs-on: ubuntu-latest
    # Trusted Publishing (OIDC): no username/password or API token needed.
    # Requires a matching "pypi" environment in the repo settings and a PyPI
    # trusted publisher configured for this repo + workflow + environment.
    environment:
      name: pypi
      url: https://pypi.org/project/django-baton/
    permissions:
      id-token: write
    steps:
    - name: Download built distributions
      uses: actions/download-artifact@v8
      with:
        name: dist
        path: dist/
    - name: Publish to PyPI
      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: Upload Python Package
 
on:
  push:
    tags:
      - '*'
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    name: Build distribution
    runs-on: latchkey-small
    steps:
    - uses: actions/checkout@v5
    - name: Set up Python
      uses: actions/setup-python@v6
      with:
        cache: 'pip'
        python-version: '3.x'
    - name: Build sdist and wheel
      run: |
        python -m pip install --upgrade pip build
        python -m build
    - name: Upload built distributions
      uses: actions/upload-artifact@v7
      with:
        name: dist
        path: dist/
 
  publish:
    timeout-minutes: 30
    name: Publish to PyPI
    needs: build
    runs-on: latchkey-small
    # Trusted Publishing (OIDC): no username/password or API token needed.
    # Requires a matching "pypi" environment in the repo settings and a PyPI
    # trusted publisher configured for this repo + workflow + environment.
    environment:
      name: pypi
      url: https://pypi.org/project/django-baton/
    permissions:
      id-token: write
    steps:
    - name: Download built distributions
      uses: actions/download-artifact@v8
      with:
        name: dist
        path: dist/
    - name: Publish to PyPI
      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.
• 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.
• 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 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