Publish Python package to PyPI workflow (epsy/clize)

The Publish Python package to PyPI workflow from epsy/clize, explained and optimized by Latchkey.

What it does

This is the Publish Python package to PyPI workflow from the epsy/clize 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 Python package to PyPI

on:
  push:
    tags:
      - v[0-9]*
  release:
    types:
      - published

jobs:
  python-ci:
    uses: epsy/python-workflows/.github/workflows/python-cd.yaml@main
    secrets:
      TEST_PYPI_API_TOKEN: ${{ secrets.TEST_PYPI_API_TOKEN }}
      PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN }}

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Publish Python package to PyPI
 
on:
  push:
    tags:
      - v[0-9]*
  release:
    types:
      - published
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  python-ci:
    timeout-minutes: 30
    uses: epsy/python-workflows/.github/workflows/python-cd.yaml@main
    secrets:
      TEST_PYPI_API_TOKEN: ${{ secrets.TEST_PYPI_API_TOKEN }}
      PYPI_API_TOKEN: ${{ secrets.PYPI_API_TOKEN }}
 

What changed

• Cancel superseded runs when a branch or PR gets a newer push.
• 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.