Release workflow (mathjax/MathJax)

The Release workflow from mathjax/MathJax, explained and optimized by Latchkey.

What it does

This is the Release workflow from the mathjax/MathJax 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: Release

on:
  release:
    types: [published]

permissions:
  contents: read
  id-token: write

jobs:
  setup:
    runs-on: ubuntu-latest
    name: Build and publish MathJax
    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - uses: pnpm/action-setup@v4
        name: Install pnpm
        with:
          version: 10
          run_install: false
        
      - uses: actions/setup-node@v4
        with:
          node-version: '24'
          registry-url: 'https://registry.npmjs.org'

      - name: Publish to npmjs
        run: pnpm publish --provenance --no-git-checks

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: Release
 
on:
  release:
    types: [published]
 
permissions:
  contents: read
  id-token: write
 
jobs:
  setup:
    timeout-minutes: 30
    runs-on: latchkey-small
    name: Build and publish MathJax
    steps:
      - name: Checkout
        uses: actions/checkout@v4
 
      - uses: pnpm/action-setup@v4
        name: Install pnpm
        with:
          version: 10
          run_install: false
        
      - uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: '24'
          registry-url: 'https://registry.npmjs.org'
 
      - name: Publish to npmjs
        run: pnpm publish --provenance --no-git-checks
 

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.

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