Skip to content
Latchkey

Maestro Pre-Releases to PyPi workflow (roboflow/maestro)

The Maestro Pre-Releases to PyPi workflow from roboflow/maestro, explained and optimized by Latchkey.

C

CI health: C - fair

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

Grade your own workflow free or run it on Latchkey →
Source: roboflow/maestro.github/workflows/publish-pre-release.ymlLicense Apache-2.0View source

What it does

This is the Maestro Pre-Releases to PyPi workflow from the roboflow/maestro 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: Maestro Pre-Releases to PyPi
on:
  push:
    tags:
      - '[0-9]+.[0-9]+[0-9]+.[0-9]+a[0-9]'
      - '[0-9]+.[0-9]+[0-9]+.[0-9]+b[0-9]'
      - '[0-9]+.[0-9]+[0-9]+.[0-9]+rc[0-9]'
      - '[0-9]+.[0-9]+.[0-9]+a[0-9]'
      - '[0-9]+.[0-9]+.[0-9]+b[0-9]'
      - '[0-9]+.[0-9]+.[0-9]+rc[0-9]'

  workflow_dispatch:

permissions: {} # Explicitly remove all permissions by default

jobs:
  publish-pre-release:
    name: Publish Pre-Release Package
    runs-on: ubuntu-latest
    environment:
      name: test
      url: https://pypi.org/project/maestro/
    timeout-minutes: 10
    permissions:
      id-token: write # Required for PyPI publishing
      contents: read # Required for checkout
    strategy:
      matrix:
        python-version: ["3.10"]
    steps:
      - name: πŸ›ŽοΈ Checkout
        uses:  actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
        with:
          ref: ${{ github.head_ref }}
      - name: 🐍 Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@42375524e23c412d93fb67b49958b491fce71c38 # v5.4.0
        with:
          python-version: ${{ matrix.python-version }}

      - name: πŸ—οΈ Build source and wheel distributions
        run: |
          python -m pip install --upgrade build twine
          python -m build
          twine check --strict dist/*

      - name: πŸš€ Publish to PyPi - Prelease
        uses: pypa/gh-action-pypi-publish@76f52bc884231f62b9a034ebfe128415bbaabdfc # v1.12.4
        with:
          attestations: 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: Maestro Pre-Releases to PyPi
on:
  push:
    tags:
      - '[0-9]+.[0-9]+[0-9]+.[0-9]+a[0-9]'
      - '[0-9]+.[0-9]+[0-9]+.[0-9]+b[0-9]'
      - '[0-9]+.[0-9]+[0-9]+.[0-9]+rc[0-9]'
      - '[0-9]+.[0-9]+.[0-9]+a[0-9]'
      - '[0-9]+.[0-9]+.[0-9]+b[0-9]'
      - '[0-9]+.[0-9]+.[0-9]+rc[0-9]'
 
  workflow_dispatch:
 
permissions: {} # Explicitly remove all permissions by default
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  publish-pre-release:
    name: Publish Pre-Release Package
    runs-on: latchkey-small
    environment:
      name: test
      url: https://pypi.org/project/maestro/
    timeout-minutes: 10
    permissions:
      id-token: write # Required for PyPI publishing
      contents: read # Required for checkout
    strategy:
      matrix:
        python-version: ["3.10"]
    steps:
      - name: πŸ›ŽοΈ Checkout
        uses:  actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
        with:
          ref: ${{ github.head_ref }}
      - name: 🐍 Set up Python ${{ matrix.python-version }}
        uses: actions/setup-python@42375524e23c412d93fb67b49958b491fce71c38 # v5.4.0
        with:
          cache: 'pip'
          python-version: ${{ matrix.python-version }}
 
      - name: πŸ—οΈ Build source and wheel distributions
        run: |
          python -m pip install --upgrade build twine
          python -m build
          twine check --strict dist/*
 
      - name: πŸš€ Publish to PyPi - Prelease
        uses: pypa/gh-action-pypi-publish@76f52bc884231f62b9a034ebfe128415bbaabdfc # v1.12.4
        with:
          attestations: true
 

What changed

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