Publish to PyPI workflow (rohitg00/kubectl-mcp-server)

The Publish to PyPI workflow from rohitg00/kubectl-mcp-server, explained and optimized by Latchkey.

CI health: C - fair

Point runs-on at Latchkey and get caching, 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: rohitg00/kubectl-mcp-server.github/workflows/publish-to-pypi.ymlLicense MITView source

What it does

This is the Publish to PyPI workflow from the rohitg00/kubectl-mcp-server 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: Publish to PyPI

on:
  release:
    types: [published]
  workflow_dispatch:

jobs:
  deploy-primary:
    name: Publish kubectl-mcp-server (primary)
    runs-on: ubuntu-latest
    environment: pypi
    permissions:
      id-token: write
      contents: write
    steps:
    - uses: actions/checkout@v4
      with:
        ref: ${{ github.ref }}

    - name: Set up Python
      uses: actions/setup-python@v5
      with:
        python-version: '3.11'

    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install build

    - name: Get version from setup.py
      id: version
      run: |
        VERSION=$(python setup.py --version)
        echo "version=$VERSION" >> $GITHUB_OUTPUT

    - name: Check if version exists on PyPI
      id: check
      run: |
        VERSION=$(python setup.py --version)
        if pip index versions kubectl-mcp-server 2>/dev/null | grep -q "$VERSION"; then
          echo "exists=true" >> $GITHUB_OUTPUT
          echo "Version $VERSION already exists on PyPI, skipping publish"
        else
          echo "exists=false" >> $GITHUB_OUTPUT
          echo "Version $VERSION not found, will publish"
        fi

    - name: Build package
      run: python -m build

    - name: Publish to PyPI
      if: steps.check.outputs.exists != 'true'
      uses: pypa/gh-action-pypi-publish@release/v1

    - name: Upload wheel to GitHub Release
      if: github.event_name == 'release'
      uses: softprops/action-gh-release@v2
      with:
        files: |
          dist/*.whl
          dist/*.tar.gz

  deploy-legacy:
    name: Publish kubectl-mcp-tool (legacy alias)
    needs: deploy-primary
    runs-on: ubuntu-latest
    environment: pypi
    permissions:
      id-token: write
      contents: write
    steps:
    - uses: actions/checkout@v4
      with:
        ref: ${{ github.ref }}

    - name: Set up Python
      uses: actions/setup-python@v5
      with:
        python-version: '3.11'

    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install build

    - name: Get version from setup_legacy.py
      id: version
      run: |
        VERSION=$(python setup_legacy.py --version)
        echo "version=$VERSION" >> $GITHUB_OUTPUT

    - name: Check if version exists on PyPI
      id: check
      run: |
        VERSION=$(python setup_legacy.py --version)
        if pip index versions kubectl-mcp-tool 2>/dev/null | grep -q "$VERSION"; then
          echo "exists=true" >> $GITHUB_OUTPUT
          echo "Version $VERSION already exists on PyPI, skipping publish"
        else
          echo "exists=false" >> $GITHUB_OUTPUT
          echo "Version $VERSION not found, will publish"
        fi

    - name: Build legacy package
      if: steps.check.outputs.exists != 'true'
      run: |
        mv setup.py setup_primary.py
        mv setup_legacy.py setup.py
        python -m build -o dist_legacy/
        mv setup.py setup_legacy.py
        mv setup_primary.py setup.py

    - name: Publish legacy package to PyPI
      if: steps.check.outputs.exists != 'true'
      uses: pypa/gh-action-pypi-publish@release/v1
      with:
        packages-dir: dist_legacy/

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 to PyPI
 
on:
  release:
    types: [published]
  workflow_dispatch:
 
jobs:
  deploy-primary:
    timeout-minutes: 30
    name: Publish kubectl-mcp-server (primary)
    runs-on: latchkey-small
    environment: pypi
    permissions:
      id-token: write
      contents: write
    steps:
    - uses: actions/checkout@v4
      with:
        ref: ${{ github.ref }}
 
    - name: Set up Python
      uses: actions/setup-python@v5
      with:
        cache: 'pip'
        python-version: '3.11'
 
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install build
 
    - name: Get version from setup.py
      id: version
      run: |
        VERSION=$(python setup.py --version)
        echo "version=$VERSION" >> $GITHUB_OUTPUT
 
    - name: Check if version exists on PyPI
      id: check
      run: |
        VERSION=$(python setup.py --version)
        if pip index versions kubectl-mcp-server 2>/dev/null | grep -q "$VERSION"; then
          echo "exists=true" >> $GITHUB_OUTPUT
          echo "Version $VERSION already exists on PyPI, skipping publish"
        else
          echo "exists=false" >> $GITHUB_OUTPUT
          echo "Version $VERSION not found, will publish"
        fi
 
    - name: Build package
      run: python -m build
 
    - name: Publish to PyPI
      if: steps.check.outputs.exists != 'true'
      uses: pypa/gh-action-pypi-publish@release/v1
 
    - name: Upload wheel to GitHub Release
      if: github.event_name == 'release'
      uses: softprops/action-gh-release@v2
      with:
        files: |
          dist/*.whl
          dist/*.tar.gz
 
  deploy-legacy:
    timeout-minutes: 30
    name: Publish kubectl-mcp-tool (legacy alias)
    needs: deploy-primary
    runs-on: latchkey-small
    environment: pypi
    permissions:
      id-token: write
      contents: write
    steps:
    - uses: actions/checkout@v4
      with:
        ref: ${{ github.ref }}
 
    - name: Set up Python
      uses: actions/setup-python@v5
      with:
        cache: 'pip'
        python-version: '3.11'
 
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install build
 
    - name: Get version from setup_legacy.py
      id: version
      run: |
        VERSION=$(python setup_legacy.py --version)
        echo "version=$VERSION" >> $GITHUB_OUTPUT
 
    - name: Check if version exists on PyPI
      id: check
      run: |
        VERSION=$(python setup_legacy.py --version)
        if pip index versions kubectl-mcp-tool 2>/dev/null | grep -q "$VERSION"; then
          echo "exists=true" >> $GITHUB_OUTPUT
          echo "Version $VERSION already exists on PyPI, skipping publish"
        else
          echo "exists=false" >> $GITHUB_OUTPUT
          echo "Version $VERSION not found, will publish"
        fi
 
    - name: Build legacy package
      if: steps.check.outputs.exists != 'true'
      run: |
        mv setup.py setup_primary.py
        mv setup_legacy.py setup.py
        python -m build -o dist_legacy/
        mv setup.py setup_legacy.py
        mv setup_primary.py setup.py
 
    - name: Publish legacy package to PyPI
      if: steps.check.outputs.exists != 'true'
      uses: pypa/gh-action-pypi-publish@release/v1
      with:
        packages-dir: dist_legacy/

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.

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.

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 softprops/action-gh-release