Node.js CI workflow (RetireJS/retire.js)

The Node.js CI workflow from RetireJS/retire.js, explained and optimized by Latchkey.

What it does

This is the Node.js CI workflow from the RetireJS/retire.js 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: Node.js CI

on:
  push:
    branches: [master]
  pull_request:
    branches: [master]

jobs:
  build:
    runs-on: ubuntu-latest
    timeout-minutes: 10

    strategy:
      matrix:
        node-version: [26.x]

    steps:
      - uses: actions/checkout@v4
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v4
        with:
          node-version: ${{ matrix.node-version }}
      - run: npm install
        working-directory: node
      - run: npm run build
        working-directory: node
      - run: npm test
        working-directory: node
      - run: ./validate
        working-directory: repository
      - name: Restore cached data for test-detection
        uses: actions/cache@v4
        id: cache-testdata
        with:
          path: repository/tmp
          key: ${{ runner.os }}-test-detection-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-test-detection-
      - run: ./test-detection.js
        working-directory: repository

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: Node.js CI
 
on:
  push:
    branches: [master]
  pull_request:
    branches: [master]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    runs-on: latchkey-small
    timeout-minutes: 10
 
    strategy:
      matrix:
        node-version: [26.x]
 
    steps:
      - uses: actions/checkout@v4
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: ${{ matrix.node-version }}
      - run: npm install
        working-directory: node
      - run: npm run build
        working-directory: node
      - run: npm test
        working-directory: node
      - run: ./validate
        working-directory: repository
      - name: Restore cached data for test-detection
        uses: actions/cache@v4
        id: cache-testdata
        with:
          path: repository/tmp
          key: ${{ runner.os }}-test-detection-${{ github.sha }}
          restore-keys: |
            ${{ runner.os }}-test-detection-
      - run: ./test-detection.js
        working-directory: repository
 

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.

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