Upload to PyPI workflow (PyCQA/autoflake)
The Upload to PyPI workflow from PyCQA/autoflake, explained and optimized by Latchkey.
CI health: F - at risk
Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Upload to PyPI workflow from the PyCQA/autoflake 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 to PyPI
on:
push:
tags:
- "*"
workflow_dispatch:
jobs:
release-build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v6.0.2
- uses: actions/setup-python@v6.2.0
with:
python-version: 3.x
- run: pip install build twine
- run: python -m build --wheel --sdist
- uses: actions/upload-artifact@v7.0.1
with:
name: release-dists
path: dist/
release-publish:
runs-on: ubuntu-latest
needs:
- release-build
permissions:
id-token: write
steps:
- uses: actions/download-artifact@v8.0.1
with:
name: release-dists
path: dist/
- uses: pypa/gh-action-pypi-publish@v1.14.0
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: Upload to PyPI on: push: tags: - "*" workflow_dispatch: concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: release-build: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v6.0.2 - uses: actions/setup-python@v6.2.0 with: cache: 'pip' python-version: 3.x - run: pip install build twine - run: python -m build --wheel --sdist - uses: actions/upload-artifact@v7.0.1 with: name: release-dists path: dist/ release-publish: timeout-minutes: 30 runs-on: latchkey-small needs: - release-build permissions: id-token: write steps: - uses: actions/download-artifact@v8.0.1 with: name: release-dists path: dist/ - uses: pypa/gh-action-pypi-publish@v1.14.0 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 useslatchkey-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.