Build wheels and publish workflow (torchmd/torchmd-net)
The Build wheels and publish workflow from torchmd/torchmd-net, 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.
What it does
This is the Build wheels and publish workflow from the torchmd/torchmd-net 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: Build wheels and publish
on:
workflow_dispatch:
workflow_call:
jobs:
build:
name: Create source distribution
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5
- uses: actions/setup-python@v6
with:
python-version: "3.13"
- name: Install cibuildwheel
run: pip install build
- name: Build pypi package
run: python -m build --sdist
- uses: actions/upload-artifact@v4
with:
name: source_dist
path: dist/*.tar.gz
publish-to-pypi:
name: >-
Publish Python π distribution π¦ to PyPI
needs:
- build
runs-on: ubuntu-latest
environment:
name: pypi
url: https://pypi.org/p/torchmd-net
permissions:
id-token: write # IMPORTANT: mandatory for trusted publishing
steps:
- name: Download all the dists
uses: actions/download-artifact@v4
with:
path: dist/
merge-multiple: true
- name: Publish distribution π¦ to PyPI
uses: pypa/gh-action-pypi-publish@release/v1
with:
password: ${{ secrets.TMDNET_PYPI_API_TOKEN }}
skip_existing: true
github-release:
name: >-
Create 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:
- name: Create GitHub Release
env:
GITHUB_TOKEN: ${{ github.token }}
run: >-
gh release create
"$GITHUB_REF_NAME"
--repo "$GITHUB_REPOSITORY"
--notes ""
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: Build wheels and publish on: workflow_dispatch: workflow_call: jobs: build: timeout-minutes: 30 name: Create source distribution runs-on: latchkey-small steps: - uses: actions/checkout@v5 - uses: actions/setup-python@v6 with: cache: 'pip' python-version: "3.13" - name: Install cibuildwheel run: pip install build - name: Build pypi package run: python -m build --sdist - uses: actions/upload-artifact@v4 with: name: source_dist path: dist/*.tar.gz publish-to-pypi: timeout-minutes: 30 name: >- Publish Python π distribution π¦ to PyPI needs: - build runs-on: latchkey-small environment: name: pypi url: https://pypi.org/p/torchmd-net permissions: id-token: write # IMPORTANT: mandatory for trusted publishing steps: - name: Download all the dists uses: actions/download-artifact@v4 with: path: dist/ merge-multiple: true - name: Publish distribution π¦ to PyPI uses: pypa/gh-action-pypi-publish@release/v1 with: password: ${{ secrets.TMDNET_PYPI_API_TOKEN }} skip_existing: true github-release: timeout-minutes: 30 name: >- Create 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: - name: Create GitHub Release env: GITHUB_TOKEN: ${{ github.token }} run: >- gh release create "$GITHUB_REF_NAME" --repo "$GITHUB_REPOSITORY" --notes ""
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.
- Add a job timeout so a hung step cannot burn hours of runner time.
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:
- 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.