Publish workflow (griptape-ai/griptape)
The Publish workflow from griptape-ai/griptape, explained and optimized by Latchkey.
A
CI health: A - excellent
Point runs-on at Latchkey and get job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Publish workflow from the griptape-ai/griptape 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: Publish
on:
release:
types: [published]
workflow_dispatch:
permissions:
contents: read
jobs:
publish-pypi:
runs-on: ubuntu-latest
strategy:
fail-fast: false
matrix:
python-version: ["3.10"]
steps:
- name: Checkout actions
uses: actions/checkout@v7
- name: Init environment
uses: ./.github/actions/init-environment
- name: uv Build
run: uv build
- name: uv Publish
run: uv publish --token ${{ secrets.PYPI_TOKEN }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Publish on: release: types: [published] workflow_dispatch: permissions: contents: read jobs: publish-pypi: timeout-minutes: 30 runs-on: latchkey-small strategy: fail-fast: false matrix: python-version: ["3.10"] steps: - name: Checkout actions uses: actions/checkout@v7 - name: Init environment uses: ./.github/actions/init-environment - name: uv Build run: uv build - name: uv Publish run: uv publish --token ${{ secrets.PYPI_TOKEN }}
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. - Add a job timeout so a hung step cannot burn hours of runner time.
This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.