Skip to content
Latchkey

Changeset Status workflow (lit/lit)

The Changeset Status workflow from lit/lit, explained and optimized by Latchkey.

C

CI health: C - fair

Point runs-on at Latchkey and get 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: lit/lit.github/workflows/changeset-status.yamlLicense BSD-3-ClauseView source

What it does

This is the Changeset Status workflow from the lit/lit repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-3-Clause license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: Changeset Status

on: [pull_request]

permissions:
  contents: read

jobs:
  # Enforce that all PRs that change packages need changesets. Changes
  # without changesets result in this job failing.
  changeset:
    runs-on: ubuntu-latest
    # Skip if author is lit-robot which means it's a release PR that doesn't
    # need this check.
    if: ${{ github.event.pull_request.user.login != 'lit-robot' }}
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0

      - uses: actions/setup-node@v3
        with:
          node-version: 24.5
          cache: 'npm'
          cache-dependency-path: package-lock.json

      - name: Checkout and NPM install
        run: |
          git checkout main
          git checkout ${{ github.sha }}
          npm ci

      - name: Changeset status
        run: npm run changeset status -- --since=main

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Changeset Status
 
on: [pull_request]
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  # Enforce that all PRs that change packages need changesets. Changes
  # without changesets result in this job failing.
  changeset:
    timeout-minutes: 30
    runs-on: latchkey-small
    # Skip if author is lit-robot which means it's a release PR that doesn't
    # need this check.
    if: ${{ github.event.pull_request.user.login != 'lit-robot' }}
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
 
      - uses: actions/setup-node@v3
        with:
          node-version: 24.5
          cache: 'npm'
          cache-dependency-path: package-lock.json
 
      - name: Checkout and NPM install
        run: |
          git checkout main
          git checkout ${{ github.sha }}
          npm ci
 
      - name: Changeset status
        run: npm run changeset status -- --since=main
 

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