Publish django-guid to PyPI 📦 workflow (snok/django-guid)

The Publish django-guid to PyPI 📦 workflow from snok/django-guid, explained and optimized by Latchkey.

What it does

This is the Publish django-guid to PyPI 📦 workflow from the snok/django-guid 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 django-guid to PyPI 📦

on:
  release:
    types: [ published ]

jobs:
  build-and-publish:
    name: Build and publish
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          python-version: "3.11"
      - run: python -m pip install --upgrade pip poetry
      - name: Build and publish
        run: |
          poetry config pypi-token.pypi ${{ secrets.pypi_password }}
          poetry publish --build --no-interaction

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: Publish django-guid to PyPI 📦
 
on:
  release:
    types: [ published ]
 
jobs:
  build-and-publish:
    timeout-minutes: 30
    name: Build and publish
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-python@v4
        with:
          cache: 'pip'
          python-version: "3.11"
      - run: python -m pip install --upgrade pip poetry
      - name: Build and publish
        run: |
          poetry config pypi-token.pypi ${{ secrets.pypi_password }}
          poetry publish --build --no-interaction
 

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.

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