Chromatic Publish workflow (opsmill/infrahub)

The Chromatic Publish workflow from opsmill/infrahub, explained and optimized by Latchkey.

What it does

This is the Chromatic Publish workflow from the opsmill/infrahub 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

---
# yamllint disable rule:truthy rule:truthy rule:line-length
name: 'Chromatic Publish'
on:
  pull_request:
    types: [opened, synchronize, reopened]
    paths:
      - 'frontend/packages/ui/**'
  push:
    branches:
      - develop
      - stable
      - release-*
    paths:
      - 'frontend/packages/ui/**'

permissions:
  contents: read

jobs:
  chromatic:
    defaults:
      run:
        working-directory: ./frontend/packages/ui
    name: Run Chromatic
    runs-on: ubuntu-latest
    steps:
      - name: Check out repository code
        uses: actions/checkout@v7
        with:
          fetch-depth: 0  # In order for Chromatic to correctly determine baseline commits, tot access the full Git history graph.
      - name: Install Node.js
        uses: actions/setup-node@v6
        with:
          node-version: 24
      - name: Install pnpm
        uses: pnpm/action-setup@v6
        with:
          version: 10
      - name: Install dependencies
        run: pnpm install --frozen-lockfile
      - name: Run Chromatic
        id: chromatic
        uses: chromaui/action@latest
        with:
          projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
          workingDir: ./frontend/packages/ui
      - name: Outputs Storybook URL
        run: |
          echo "Storybook URL: ${{ steps.chromatic.outputs.storybookUrl }}"

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.

---
# yamllint disable rule:truthy rule:truthy rule:line-length
name: 'Chromatic Publish'
on:
  pull_request:
    types: [opened, synchronize, reopened]
    paths:
      - 'frontend/packages/ui/**'
  push:
    branches:
      - develop
      - stable
      - release-*
    paths:
      - 'frontend/packages/ui/**'
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  chromatic:
    timeout-minutes: 30
    defaults:
      run:
        working-directory: ./frontend/packages/ui
    name: Run Chromatic
    runs-on: latchkey-small
    steps:
      - name: Check out repository code
        uses: actions/checkout@v7
        with:
          fetch-depth: 0  # In order for Chromatic to correctly determine baseline commits, tot access the full Git history graph.
      - name: Install Node.js
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 24
      - name: Install pnpm
        uses: pnpm/action-setup@v6
        with:
          version: 10
      - name: Install dependencies
        run: pnpm install --frozen-lockfile
      - name: Run Chromatic
        id: chromatic
        uses: chromaui/action@latest
        with:
          projectToken: ${{ secrets.CHROMATIC_PROJECT_TOKEN }}
          workingDir: ./frontend/packages/ui
      - name: Outputs Storybook URL
        run: |
          echo "Storybook URL: ${{ steps.chromatic.outputs.storybookUrl }}"
 

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.

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