Upload wrf-python to PyPI workflow (NCAR/wrf-python)

The Upload wrf-python to PyPI workflow from NCAR/wrf-python, explained and optimized by Latchkey.

CI health: C - fair

Point runs-on at Latchkey and get caching, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →

Source: NCAR/wrf-python.github/workflows/pypi.yamlLicense Apache-2.0View source

What it does

This is the Upload wrf-python to PyPI workflow from the NCAR/wrf-python repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

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

The workflow

workflow (.yml)

name: Upload wrf-python to PyPI
on:
  release:
    types:
      - published
jobs:
  test-build:
    if: github.repository == 'NCAR/wrf-python'
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          python-version: '3.10'
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install build twine
      - name: Build tarball and wheels
        run: |
          python -m build
      - name: Test the artifacts
        run: |
          python -m twine check dist/*
  publish:
    needs: test-build
    if: startsWith(github.ref, 'refs/tags')
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          python-version: '3.10'
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install build twine
      - name: Build tarball and wheels
        run: |
          python -m build
      - name: Test the artifacts
        run: |
          python -m twine check dist/*
      - name: Publish package to PyPI
        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
        with:
          user: __token__
          password: ${{ secrets.PYPI_WRF_PYTHON }}
          skip_existing: true
          verbose: 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 wrf-python to PyPI
on:
  release:
    types:
      - published
jobs:
  test-build:
    timeout-minutes: 30
    if: github.repository == 'NCAR/wrf-python'
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v6
      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: '3.10'
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install build twine
      - name: Build tarball and wheels
        run: |
          python -m build
      - name: Test the artifacts
        run: |
          python -m twine check dist/*
  publish:
    timeout-minutes: 30
    needs: test-build
    if: startsWith(github.ref, 'refs/tags')
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v6
      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: '3.10'
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          python -m pip install build twine
      - name: Build tarball and wheels
        run: |
          python -m build
      - name: Test the artifacts
        run: |
          python -m twine check dist/*
      - name: Publish package to PyPI
        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
        with:
          user: __token__
          password: ${{ secrets.PYPI_WRF_PYTHON }}
          skip_existing: true
          verbose: 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 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 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow

actions/checkout actions/setup-python