CI workflow (bfirsh/jsnes)
The CI workflow from bfirsh/jsnes, explained and optimized by Latchkey.
CI health: D - needs work
Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the CI workflow from the bfirsh/jsnes 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: CI
on: [push, pull_request]
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Use Node.js
uses: actions/setup-node@v4
with:
node-version: '24.x'
- run: npm ci
- run: npm run build
- run: npm test
web:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Use Node.js
uses: actions/setup-node@v4
with:
node-version: '24.x'
- run: npm ci
working-directory: web
- run: npm run build
working-directory: web
- run: npm test
working-directory: web
publish:
if: startsWith(github.ref, 'refs/tags/v')
needs: [build, web]
runs-on: ubuntu-latest
permissions:
contents: read
id-token: write
steps:
- uses: actions/checkout@v4
- name: Use Node.js
uses: actions/setup-node@v4
with:
node-version: '24.x'
- run: npm ci
# Trusted publishing via OIDC - no NPM_TOKEN needed.
# Configure the trusted publisher on npmjs.com to allow this repo/workflow.
# See https://docs.npmjs.com/trusted-publishers
- run: npm publish --provenance --access public
env:
NODE_AUTH_TOKEN: ""
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: CI on: [push, pull_request] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v4 - name: Use Node.js uses: actions/setup-node@v4 with: cache: 'npm' node-version: '24.x' - run: npm ci - run: npm run build - run: npm test web: timeout-minutes: 30 runs-on: latchkey-small steps: - uses: actions/checkout@v4 - name: Use Node.js uses: actions/setup-node@v4 with: cache: 'npm' node-version: '24.x' - run: npm ci working-directory: web - run: npm run build working-directory: web - run: npm test working-directory: web publish: timeout-minutes: 30 if: startsWith(github.ref, 'refs/tags/v') needs: [build, web] runs-on: latchkey-small permissions: contents: read id-token: write steps: - uses: actions/checkout@v4 - name: Use Node.js uses: actions/setup-node@v4 with: cache: 'npm' node-version: '24.x' - run: npm ci # Trusted publishing via OIDC - no NPM_TOKEN needed. # Configure the trusted publisher on npmjs.com to allow this repo/workflow. # See https://docs.npmjs.com/trusted-publishers - run: npm publish --provenance --access public env: NODE_AUTH_TOKEN: ""
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 useslatchkey-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.
- 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 3 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.