Track pathological reference workflow (markdown-it/markdown-it)

The Track pathological reference workflow from markdown-it/markdown-it, explained and optimized by Latchkey.

What it does

This is the Track pathological reference workflow from the markdown-it/markdown-it 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: Track pathological reference

on:
  workflow_dispatch:
  schedule:
    - cron: '0 0 * * 3'

jobs:
  track-ref-pathological:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v5

    - name: Use Node.js 24
      uses: actions/setup-node@v6
      with:
        node-version: 24

    - run: npm install

    - name: Track pathological reference
      run: npm run pathological:track-ref

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: Track pathological reference
 
on:
  workflow_dispatch:
  schedule:
    - cron: '0 0 * * 3'
 
jobs:
  track-ref-pathological:
    timeout-minutes: 30
    runs-on: latchkey-small
 
    steps:
    - uses: actions/checkout@v5
 
    - name: Use Node.js 24
      uses: actions/setup-node@v6
      with:
        cache: 'npm'
        node-version: 24
 
    - run: npm install
 
    - name: Track pathological reference
      run: npm run pathological:track-ref
 

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