Publish to PyPI workflow (gmr/rabbitpy)

The Publish to PyPI workflow from gmr/rabbitpy, explained and optimized by Latchkey.

What it does

This is the Publish to PyPI workflow from the gmr/rabbitpy repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: Publish to PyPI

on:
  release:
    types: [published]

jobs:
  deploy:
    runs-on: ubuntu-latest

    environment:
      name: pypi
      url: https://pypi.org/project/rabbitpy/

    permissions:
      contents: read
      id-token: write

    steps:
      - uses: actions/checkout@v5

      - name: Install uv
        uses: astral-sh/setup-uv@v6

      - name: Build and check package
        run: |
          uv build
          uvx twine check dist/*

      - name: Publish package distributions to PyPI
        uses: pypa/gh-action-pypi-publish@release/v1

The same workflow, on Latchkey

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

name: Publish to PyPI
 
on:
  release:
    types: [published]
 
jobs:
  deploy:
    timeout-minutes: 30
    runs-on: latchkey-small
 
    environment:
      name: pypi
      url: https://pypi.org/project/rabbitpy/
 
    permissions:
      contents: read
      id-token: write
 
    steps:
      - uses: actions/checkout@v5
 
      - name: Install uv
        uses: astral-sh/setup-uv@v6
 
      - name: Build and check package
        run: |
          uv build
          uvx twine check dist/*
 
      - name: Publish package distributions 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.
• Add a job timeout so a hung step cannot burn hours of runner time.

2 third-party actions are referenced by a movable tag. Pin them 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.

Actions used in this workflow