publish workflow (svg/svgo)

The publish workflow from svg/svgo, explained and optimized by Latchkey.

CI health: C - fair

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

Grade your own workflow free or run it on Latchkey →

Source: svg/svgo.github/workflows/publish.ymlLicense MITView source

What it does

This is the publish workflow from the svg/svgo 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

workflow (.yml)

on:
  release:
    types: [created]
  workflow_dispatch:

permissions:
  id-token: write
  contents: read

jobs:
  publish-npm:
    runs-on: ubuntu-latest
    env:
      GH_TOKEN: ${{ github.token }}
    steps:
      - uses: actions/checkout@v6
      - run: corepack enable
      - uses: actions/setup-node@v6
        with:
          node-version: 24
          registry-url: https://registry.npmjs.org
      - run: yarn install
      - run: |
          VERSION=$(jq -r .version <package.json)
          if [[ "$VERSION" = *"-rc."* ]]; then
            yarn npm publish --access public --tag rc
          else
            LATEST_VERSION="$(gh release view --json tagName -q '.tagName' --repo ${{ github.repository }})"
            if [[ "${{ github.ref_name }}" = "$LATEST_VERSION" ]]; then
              yarn npm publish --access public
            else
              MAJOR="$(awk -F '.' '{ print $1 }' <<< "$VERSION")"
              yarn npm publish --access public --tag "v$MAJOR"
            fi
          fi

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.

on:
  release:
    types: [created]
  workflow_dispatch:
 
permissions:
  id-token: write
  contents: read
 
jobs:
  publish-npm:
    timeout-minutes: 30
    runs-on: latchkey-small
    env:
      GH_TOKEN: ${{ github.token }}
    steps:
      - uses: actions/checkout@v6
      - run: corepack enable
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 24
          registry-url: https://registry.npmjs.org
      - run: yarn install
      - run: |
          VERSION=$(jq -r .version <package.json)
          if [[ "$VERSION" = *"-rc."* ]]; then
            yarn npm publish --access public --tag rc
          else
            LATEST_VERSION="$(gh release view --json tagName -q '.tagName' --repo ${{ github.repository }})"
            if [[ "${{ github.ref_name }}" = "$LATEST_VERSION" ]]; then
              yarn npm publish --access public
            else
              MAJOR="$(awk -F '.' '{ print $1 }' <<< "$VERSION")"
              yarn npm publish --access public --tag "v$MAJOR"
            fi
          fi

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.

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

actions/checkout actions/setup-node