Skip to content
Latchkey

Run pnpm evals workflow (braintrustdata/autoevals)

The Run pnpm evals workflow from braintrustdata/autoevals, explained and optimized by Latchkey.

D

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.

Grade your own workflow free or run it on Latchkey →
Source: braintrustdata/autoevals.github/workflows/eval.yamlLicense MITView source

What it does

This is the Run pnpm evals workflow from the braintrustdata/autoevals 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

workflow (.yml)
name: Run pnpm evals

on:
  pull_request:
    # Uncomment to run only when files in the 'evals' directory change
    # paths:
    #   - "evals/**"
  push:
    branches: [main]
    # Uncomment to run only when files in the 'evals' directory change
    # paths:
    #   - "evals/**"

permissions:
  pull-requests: write
  contents: read

jobs:
  eval:
    name: Run evals
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        id: checkout
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          fetch-depth: 0

      - name: Setup Node.js
        id: setup-node
        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
        with:
          node-version: 22

      - name: Setup pnpm
        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5.0.0
        with:
          version: 10.33.0

      - name: Install Dependencies
        id: install
        run: pnpm install --frozen-lockfile

      - name: Build packages
        id: build
        run: pnpm build

      - name: Run Evals
        uses: braintrustdata/eval-action@c0dd75b29984a0cc63a827d6e8da2f23f2752be4 # v1.0.16
        with:
          api_key: ${{ secrets.BRAINTRUST_API_KEY }}
          runtime: node
          root: evals

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: Run pnpm evals
 
on:
  pull_request:
    # Uncomment to run only when files in the 'evals' directory change
    # paths:
    #   - "evals/**"
  push:
    branches: [main]
    # Uncomment to run only when files in the 'evals' directory change
    # paths:
    #   - "evals/**"
 
permissions:
  pull-requests: write
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  eval:
    timeout-minutes: 30
    name: Run evals
    runs-on: latchkey-small
 
    steps:
      - name: Checkout
        id: checkout
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          fetch-depth: 0
 
      - name: Setup Node.js
        id: setup-node
        uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
        with:
          cache: 'npm'
          node-version: 22
 
      - name: Setup pnpm
        uses: pnpm/action-setup@fc06bc1257f339d1d5d8b3a19a8cae5388b55320 # v5.0.0
        with:
          version: 10.33.0
 
      - name: Install Dependencies
        id: install
        run: pnpm install --frozen-lockfile
 
      - name: Build packages
        id: build
        run: pnpm build
 
      - name: Run Evals
        uses: braintrustdata/eval-action@c0dd75b29984a0cc63a827d6e8da2f23f2752be4 # v1.0.16
        with:
          api_key: ${{ secrets.BRAINTRUST_API_KEY }}
          runtime: node
          root: evals
 

What changed

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:

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