CI workflow (Ripple-TS/ripple)
The CI workflow from Ripple-TS/ripple, explained and optimized by Latchkey.
CI health: F - at risk
Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the CI workflow from the Ripple-TS/ripple 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: CI
on:
push:
branches: [main, develop]
tags: ["!**"]
paths:
- "packages/**"
- "package.json"
- "pnpm-lock.yaml"
- "pnpm-workspace.yaml"
- "scripts/**"
- "vitest.config.js"
- ".changeset/**"
- ".github/workflows/ci.yml"
pull_request:
branches: [main, develop]
paths:
- "packages/**"
- "package.json"
- "pnpm-lock.yaml"
- "pnpm-workspace.yaml"
- "scripts/**"
- "vitest.config.js"
- ".changeset/**"
- ".github/workflows/ci.yml"
jobs:
test:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [22, 24, 26]
steps:
- name: Checkout code
uses: actions/checkout@v6
- name: Install pnpm
uses: pnpm/action-setup@v6
- name: Setup Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v6
with:
node-version: ${{ matrix.node-version }}
cache: "pnpm"
- name: Install dependencies
run: pnpm install --prod false --frozen-lockfile
- name: Build cli
working-directory: ./packages/cli
run: pnpm build
- name: Build eslint-parser
working-directory: ./packages/eslint-parser
run: pnpm build
- name: Run tests
run: pnpm test
- name: Upload test results
uses: actions/upload-artifact@v7
if: failure()
with:
name: test-results-node-${{ matrix.node-version }}
path: |
packages/ripple/tests/__snapshots__/
coverage/
retention-days: 30
lint:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v6
- name: Install pnpm
uses: pnpm/action-setup@v6
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: 24
cache: "pnpm"
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Check formatting
run: pnpm format:check
changeset-check:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v6
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: 24
- name: Disallow major and minor bumps in changesets
run: node scripts/check-changesets.js
typecheck:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v6
- name: Install pnpm
uses: pnpm/action-setup@v6
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: 24
cache: "pnpm"
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Type check
run: pnpm typecheck
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: branches: [main, develop] tags: ["!**"] paths: - "packages/**" - "package.json" - "pnpm-lock.yaml" - "pnpm-workspace.yaml" - "scripts/**" - "vitest.config.js" - ".changeset/**" - ".github/workflows/ci.yml" pull_request: branches: [main, develop] paths: - "packages/**" - "package.json" - "pnpm-lock.yaml" - "pnpm-workspace.yaml" - "scripts/**" - "vitest.config.js" - ".changeset/**" - ".github/workflows/ci.yml" concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: test: timeout-minutes: 30 runs-on: latchkey-small strategy: matrix: node-version: [22, 24, 26] steps: - name: Checkout code uses: actions/checkout@v6 - name: Install pnpm uses: pnpm/action-setup@v6 - name: Setup Node.js ${{ matrix.node-version }} uses: actions/setup-node@v6 with: node-version: ${{ matrix.node-version }} cache: "pnpm" - name: Install dependencies run: pnpm install --prod false --frozen-lockfile - name: Build cli working-directory: ./packages/cli run: pnpm build - name: Build eslint-parser working-directory: ./packages/eslint-parser run: pnpm build - name: Run tests run: pnpm test - name: Upload test results uses: actions/upload-artifact@v7 if: failure() with: name: test-results-node-${{ matrix.node-version }} path: | packages/ripple/tests/__snapshots__/ coverage/ retention-days: 30 lint: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout code uses: actions/checkout@v6 - name: Install pnpm uses: pnpm/action-setup@v6 - name: Setup Node.js uses: actions/setup-node@v6 with: node-version: 24 cache: "pnpm" - name: Install dependencies run: pnpm install --frozen-lockfile - name: Check formatting run: pnpm format:check changeset-check: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout code uses: actions/checkout@v6 - name: Setup Node.js uses: actions/setup-node@v6 with: cache: 'npm' node-version: 24 - name: Disallow major and minor bumps in changesets run: node scripts/check-changesets.js typecheck: timeout-minutes: 30 runs-on: latchkey-small steps: - name: Checkout code uses: actions/checkout@v6 - name: Install pnpm uses: pnpm/action-setup@v6 - name: Setup Node.js uses: actions/setup-node@v6 with: node-version: 24 cache: "pnpm" - name: Install dependencies run: pnpm install --frozen-lockfile - name: Type check run: pnpm typecheck
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.
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.
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 4 jobs (6 with the matrix expanded) per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.