Publish Python π distribution π¦ to PyPI and TestPyPI workflow (SecretiveShell/MCP-Bridge)
The Publish Python π distribution π¦ to PyPI and TestPyPI workflow from SecretiveShell/MCP-Bridge, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get caching, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Publish Python π distribution π¦ to PyPI and TestPyPI workflow from the SecretiveShell/MCP-Bridge 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 Python π distribution π¦ to PyPI and TestPyPI
on:
#push:
# branches:
# - main
workflow_dispatch:
inputs:
version_bump:
type: choice
description: 'Choose the type of version bump (major, minor, patch)'
required: true
default: 'minor'
options:
- major
- minor
- patch
- alpha
- beta
- rc
- rev
- post
jobs:
build:
name: Build distribution π¦
runs-on: ubuntu-latest
outputs:
new_tag: ${{ steps.set_var.outputs.new_tag }}
permissions:
contents: write # IMPORTANT: mandatory for making GitHub Releases
id-token: write # IMPORTANT: mandatory for trusted publishing
steps:
- uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.x"
- name: Install pypa/build
run: >-
python3 -m
pip install
hatchling uv
--user
- name: update version tag in pyproject.toml
id: set_var
run: |
hatchling version ${{ github.event.inputs.version_bump }}
echo "new_tag=$(hatchling version)" >> $GITHUB_OUTPUT
git config --global user.email "gha@github.com"
git config --global user.name "github robot"
git commit -am "update package build version gha"
git push origin master
- name: Build a binary wheel and a source tarball
run: uv build && uv publish
- name: Store the distribution packages
uses: actions/upload-artifact@v4
with:
name: python-package-distributions
path: dist/
github-release:
name: >-
Sign the Python π distribution π¦ with Sigstore
and upload them to GitHub Release
needs:
- build
runs-on: ubuntu-latest
permissions:
contents: write # IMPORTANT: mandatory for making GitHub Releases
id-token: write # IMPORTANT: mandatory for sigstore
steps:
- uses: actions/checkout@v4
- name: Download all the dists
uses: actions/download-artifact@v4.3.0
with:
name: python-package-distributions
path: .
- name: Sign the dists with Sigstore
uses: sigstore/gh-action-sigstore-python@v3.0.1
with:
inputs: >-
./*.tar.gz
./*.whl
- name: Create GitHub Release
env:
GITHUB_TOKEN: ${{ github.token }}
run: >-
gh release create
'${{ needs.build.outputs.new_tag }}'
--repo '${{ github.repository }}'
--generate-notes
- name: Upload artifact signatures to GitHub Release
env:
GITHUB_TOKEN: ${{ github.token }}
# Upload to GitHub Release using the `gh` CLI.
# `dist/` contains the built packages, and the
# sigstore-produced signatures and certificates.
run: >-
gh release upload
'${{ needs.build.outputs.new_tag }}' ./*.tar.gz ./*.whl ./*.tar.gz.sigstore.json ./*.whl.sigstore.json
--repo '${{ github.repository }}'
push-store-image:
permissions: write-all
runs-on: ubuntu-latest
needs:
- build
steps:
- name: Login to GitHub Container Registry
uses: docker/login-action@v3
with:
registry: ghcr.io
username: ${{ github.actor }}
password: ${{ secrets.GITHUB_TOKEN }}
- name: Checkout code
uses: actions/checkout@v4
- name: 'Build images'
run: |
RELEASE=${{ needs.build.outputs.new_tag }} \
docker buildx bake mcp-bridge -f docker-bake.hcl --push
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 Python π distribution π¦ to PyPI and TestPyPI on: #push: # branches: # - main workflow_dispatch: inputs: version_bump: type: choice description: 'Choose the type of version bump (major, minor, patch)' required: true default: 'minor' options: - major - minor - patch - alpha - beta - rc - rev - post jobs: build: name: Build distribution π¦ runs-on: latchkey-small outputs: new_tag: ${{ steps.set_var.outputs.new_tag }} permissions: contents: write # IMPORTANT: mandatory for making GitHub Releases id-token: write # IMPORTANT: mandatory for trusted publishing steps: - uses: actions/checkout@v4 - name: Set up Python uses: actions/setup-python@v5 with: cache: 'pip' python-version: "3.x" - name: Install pypa/build run: >- python3 -m pip install hatchling uv --user - name: update version tag in pyproject.toml id: set_var run: | hatchling version ${{ github.event.inputs.version_bump }} echo "new_tag=$(hatchling version)" >> $GITHUB_OUTPUT git config --global user.email "gha@github.com" git config --global user.name "github robot" git commit -am "update package build version gha" git push origin master - name: Build a binary wheel and a source tarball run: uv build && uv publish - name: Store the distribution packages uses: actions/upload-artifact@v4 with: name: python-package-distributions path: dist/ github-release: name: >- Sign the Python π distribution π¦ with Sigstore and upload them to GitHub Release needs: - build runs-on: latchkey-small permissions: contents: write # IMPORTANT: mandatory for making GitHub Releases id-token: write # IMPORTANT: mandatory for sigstore steps: - uses: actions/checkout@v4 - name: Download all the dists uses: actions/download-artifact@v4.3.0 with: name: python-package-distributions path: . - name: Sign the dists with Sigstore uses: sigstore/gh-action-sigstore-python@v3.0.1 with: inputs: >- ./*.tar.gz ./*.whl - name: Create GitHub Release env: GITHUB_TOKEN: ${{ github.token }} run: >- gh release create '${{ needs.build.outputs.new_tag }}' --repo '${{ github.repository }}' --generate-notes - name: Upload artifact signatures to GitHub Release env: GITHUB_TOKEN: ${{ github.token }} # Upload to GitHub Release using the `gh` CLI. # `dist/` contains the built packages, and the # sigstore-produced signatures and certificates. run: >- gh release upload '${{ needs.build.outputs.new_tag }}' ./*.tar.gz ./*.whl ./*.tar.gz.sigstore.json ./*.whl.sigstore.json --repo '${{ github.repository }}' push-store-image: permissions: write-all runs-on: latchkey-small needs: - build steps: - name: Login to GitHub Container Registry uses: docker/login-action@v3 with: registry: ghcr.io username: ${{ github.actor }} password: ${{ secrets.GITHUB_TOKEN }} - name: Checkout code uses: actions/checkout@v4 - name: 'Build images' run: | RELEASE=${{ needs.build.outputs.new_tag }} \ docker buildx bake mcp-bridge -f docker-bake.hcl --push
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 useslatchkey-small; pick the runner size that fits the job. - Cache dependency installs on the setup step so they are served from cache.
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 3 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.