Node.js (Windows) CI workflow (hubotio/hubot)

The Node.js (Windows) CI workflow from hubotio/hubot, explained and optimized by Latchkey.

What it does

This is the Node.js (Windows) CI workflow from the hubotio/hubot 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: Node.js (Windows) CI
permissions:
  contents: read
  issues: read
on:
  push:
    branches:
      - main
  schedule:
    - cron: '5 4 * * 0'
jobs:
  npm-test:
    runs-on: windows-latest
    strategy:
      matrix:
        node-version: [23.x]
    steps:
    - uses: actions/checkout@v4
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v4
      with:
        node-version: ${{ matrix.node-version }}
        cache: 'npm'
    - run: npm ci
    - name: Run Tests
      env:
        HUBOT_LOG_LEVEL: debug
      run: npm test --experimental-strip-types

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Node.js (Windows) CI
permissions:
  contents: read
  issues: read
on:
  push:
    branches:
      - main
  schedule:
    - cron: '5 4 * * 0'
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  npm-test:
    timeout-minutes: 30
    runs-on: windows-latest
    strategy:
      matrix:
        node-version: [23.x]
    steps:
    - uses: actions/checkout@v4
    - name: Use Node.js ${{ matrix.node-version }}
      uses: actions/setup-node@v4
      with:
        node-version: ${{ matrix.node-version }}
        cache: 'npm'
    - run: npm ci
    - name: Run Tests
      env:
        HUBOT_LOG_LEVEL: debug
      run: npm test --experimental-strip-types
 

What changed

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