Smoke test workflow (sindresorhus/eslint-plugin-unicorn)

The Smoke test workflow from sindresorhus/eslint-plugin-unicorn, explained and optimized by Latchkey.

What it does

This is the Smoke test workflow from the sindresorhus/eslint-plugin-unicorn 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: Smoke test

on:
  # Disabled until `AriPerkkio/eslint-remote-tester-run-action` runs on Node.js 22.
  # schedule:
  #   - cron: "0 0 * * SUN"
  workflow_dispatch:

jobs:
  lint:
    if: ${{ false }}
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v6
      - uses: actions/setup-node@v6
      - run: npm install --legacy-peer-deps
      - uses: AriPerkkio/eslint-remote-tester-run-action@v5
        with:
          issue-title: "Results of weekly scheduled smoke test"
          eslint-remote-tester-config: test/smoke/eslint-remote-tester.config.js

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: Smoke test
 
on:
  # Disabled until `AriPerkkio/eslint-remote-tester-run-action` runs on Node.js 22.
  # schedule:
  #   - cron: "0 0 * * SUN"
  workflow_dispatch:
 
jobs:
  lint:
    timeout-minutes: 30
    if: ${{ false }}
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v6
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
      - run: npm install --legacy-peer-deps
      - uses: AriPerkkio/eslint-remote-tester-run-action@v5
        with:
          issue-title: "Results of weekly scheduled smoke test"
          eslint-remote-tester-config: test/smoke/eslint-remote-tester.config.js
 

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.

1 third-party action is referenced by a movable tag. Pin it 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