wizarr-ci # main “code + Docker” pipeline workflow (wizarrrr/wizarr)

The wizarr-ci # main “code + Docker” pipeline workflow from wizarrrr/wizarr, explained and optimized by Latchkey.

What it does

This is the wizarr-ci # main “code + Docker” pipeline workflow from the wizarrrr/wizarr 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: wizarr-ci   # main “code + Docker” pipeline

on:
  push:
    branches: [ main ]
    paths-ignore:     # skip pure-translation commits
      - 'app/translations/**'
      - .github/
  workflow_dispatch: {}   # manual run

env:
  PYTHON_VERSION: '3.13'
  NODE_VERSION:  '20'

jobs:
  docker-dev:
    runs-on: ubuntu-24.04
    permissions:
      contents: read
      packages: write

    steps:
      - uses: actions/checkout@v7

      # ─────── Generate uv.lock for reproducible builds ───────
      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          python-version: ${{ env.PYTHON_VERSION }}

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

      - name: Generate uv.lock
        run: uv lock

      # ─────── Docker bits ───────
      - name: Log in to GHCR
        uses: docker/login-action@v4
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Set up QEMU
        uses: docker/setup-qemu-action@v4

      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v4

      - name: Build & push multi-arch :dev image
        uses: docker/build-push-action@v7
        with:
          context: .
          push: true
          platforms: linux/amd64,linux/arm64
          tags: ghcr.io/${{ github.repository_owner }}/wizarr:dev

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: wizarr-ci   # main “code + Docker” pipeline
 
on:
  push:
    branches: [ main ]
    paths-ignore:     # skip pure-translation commits
      - 'app/translations/**'
      - .github/
  workflow_dispatch: {}   # manual run
 
env:
  PYTHON_VERSION: '3.13'
  NODE_VERSION:  '20'
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  docker-dev:
    timeout-minutes: 30
    runs-on: latchkey-small
    permissions:
      contents: read
      packages: write
 
    steps:
      - uses: actions/checkout@v7
 
      # ─────── Generate uv.lock for reproducible builds ───────
      - name: Set up Python
        uses: actions/setup-python@v6
        with:
          cache: 'pip'
          python-version: ${{ env.PYTHON_VERSION }}
 
      - name: Install uv
        uses: astral-sh/setup-uv@v7
 
      - name: Generate uv.lock
        run: uv lock
 
      # ─────── Docker bits ───────
      - name: Log in to GHCR
        uses: docker/login-action@v4
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
 
      - name: Set up QEMU
        uses: docker/setup-qemu-action@v4
 
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v4
 
      - name: Build & push multi-arch :dev image
        uses: docker/build-push-action@v7
        with:
          context: .
          push: true
          platforms: linux/amd64,linux/arm64
          tags: ghcr.io/${{ github.repository_owner }}/wizarr:dev
 

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.
• Cancel superseded runs when a branch or PR gets a newer push.
• 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.

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

• Container pulls and builds

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