Release workflow (datachain-ai/datachain)

The Release workflow from datachain-ai/datachain, explained and optimized by Latchkey.

What it does

This is the Release workflow from the datachain-ai/datachain 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

name: Release

on:
  release:
    types: [published]
  workflow_dispatch:

env:
  FORCE_COLOR: "1"

jobs:
  release:
    environment: pypi
    permissions:
      contents: read
      id-token: write
    runs-on: ubuntu-latest
    steps:
      - name: Check out the repository
        uses: actions/checkout@v7
        with:
          fetch-depth: 0

      - name: Set up Python 3.13
        uses: actions/setup-python@v6
        with:
          python-version: '3.13'

      - name: Setup uv
        uses: astral-sh/setup-uv@v7

      - name: Install nox
        run: uv pip install nox --system
      - name: Build package
        run: nox -s build

      - name: Upload package
        if: github.event_name == 'release'
        uses: pypa/gh-action-pypi-publish@release/v1

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: Release
 
on:
  release:
    types: [published]
  workflow_dispatch:
 
env:
  FORCE_COLOR: "1"
 
jobs:
  release:
    timeout-minutes: 30
    environment: pypi
    permissions:
      contents: read
      id-token: write
    runs-on: latchkey-small
    steps:
      - name: Check out the repository
        uses: actions/checkout@v7
        with:
          fetch-depth: 0
 
      - name: Set up Python 3.13
        uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: '3.13'
 
      - name: Setup uv
        uses: astral-sh/setup-uv@v7
 
      - name: Install nox
        run: uv pip install nox --system
      - name: Build package
        run: nox -s build
 
      - name: Upload package
        if: github.event_name == 'release'
        uses: pypa/gh-action-pypi-publish@release/v1
 

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 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