Skip to content
Latchkey

Upload Python Package workflow (ranahaani/GNews)

The Upload Python Package workflow from ranahaani/GNews, explained and optimized by Latchkey.

F

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.

Grade your own workflow free or run it on Latchkey →
Source: ranahaani/GNews.github/workflows/python-publish.ymlLicense MITView source

What it does

This is the Upload Python Package workflow from the ranahaani/GNews 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

workflow (.yml)
name: Upload Python Package

on:
  push:
    branches:
      - master

jobs:
  pypi-publish:
    name: Publish release to PyPI
    runs-on: ubuntu-latest
    environment:
      name: pypi
      url: https://pypi.org/p/gnews
    permissions:
      id-token: write

    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 2

      - name: Check if setup.py changed
        id: check
        run: |
          if git diff HEAD~1 HEAD -- setup.py | grep -q .; then
            echo "changed=true" >> $GITHUB_OUTPUT
          else
            echo "changed=false" >> $GITHUB_OUTPUT
          fi

      - name: Set up Python
        if: steps.check.outputs.changed == 'true'
        uses: actions/setup-python@v5
        with:
          python-version: "3.x"

      - name: Install dependencies
        if: steps.check.outputs.changed == 'true'
        run: |
          python -m pip install --upgrade pip
          pip install setuptools wheel

      - name: Build package
        if: steps.check.outputs.changed == 'true'
        run: python setup.py sdist bdist_wheel

      - name: Publish package distributions to PyPI
        if: steps.check.outputs.changed == 'true'
        uses: pypa/gh-action-pypi-publish@release/v1
        with:
          password: ${{ secrets.PYPI_API_TOKEN }}

      - name: Skip - setup.py unchanged
        if: steps.check.outputs.changed == 'false'
        run: echo "setup.py not changed - skipping PyPI publish"

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:
    branches:
      - master
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  pypi-publish:
    timeout-minutes: 30
    name: Publish release to PyPI
    runs-on: latchkey-small
    environment:
      name: pypi
      url: https://pypi.org/p/gnews
    permissions:
      id-token: write
 
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 2
 
      - name: Check if setup.py changed
        id: check
        run: |
          if git diff HEAD~1 HEAD -- setup.py | grep -q .; then
            echo "changed=true" >> $GITHUB_OUTPUT
          else
            echo "changed=false" >> $GITHUB_OUTPUT
          fi
 
      - name: Set up Python
        if: steps.check.outputs.changed == 'true'
        uses: actions/setup-python@v5
        with:
          cache: 'pip'
          python-version: "3.x"
 
      - name: Install dependencies
        if: steps.check.outputs.changed == 'true'
        run: |
          python -m pip install --upgrade pip
          pip install setuptools wheel
 
      - name: Build package
        if: steps.check.outputs.changed == 'true'
        run: python setup.py sdist bdist_wheel
 
      - name: Publish package distributions to PyPI
        if: steps.check.outputs.changed == 'true'
        uses: pypa/gh-action-pypi-publish@release/v1
        with:
          password: ${{ secrets.PYPI_API_TOKEN }}
 
      - name: Skip - setup.py unchanged
        if: steps.check.outputs.changed == 'false'
        run: echo "setup.py not changed - skipping PyPI publish"
 

What changed

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:

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