Release workflow (tailwindlabs/tailwindcss-typography)
The Release workflow from tailwindlabs/tailwindcss-typography, explained and optimized by Latchkey.
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.
What it does
This is the Release workflow from the tailwindlabs/tailwindcss-typography 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: Release
on:
push:
branches: [main]
release:
types: [published]
permissions:
contents: read
id-token: write
jobs:
build:
runs-on: ubuntu-latest
strategy:
matrix:
node-version: [24]
steps:
- uses: actions/checkout@v4
- name: Use Node.js ${{ matrix.node-version }}
uses: actions/setup-node@v4
with:
node-version: ${{ matrix.node-version }}
registry-url: 'https://registry.npmjs.org'
cache: 'npm'
- name: Install dependencies
run: npm install
- name: Test
run: npm test
- name: Resolve release metadata
run: |
if [ "${{ github.event_name }}" = "release" ]; then
echo "RELEASE_KIND=release" >> $GITHUB_ENV
echo "RELEASE_CHANNEL=$(npm run release-channel --silent)" >> $GITHUB_ENV
else
echo "RELEASE_KIND=insiders" >> $GITHUB_ENV
echo "INSIDERS_VERSION=0.0.0-insiders.$(git rev-parse --short HEAD)" >> $GITHUB_ENV
echo "RELEASE_CHANNEL=insiders" >> $GITHUB_ENV
fi
- name: Version based on commit
if: env.RELEASE_KIND == 'insiders'
run: npm version "$INSIDERS_VERSION" --force --no-git-tag-version
- name: Publish
run: npm publish --provenance --tag "$RELEASE_CHANNEL"
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Release on: push: branches: [main] release: types: [published] permissions: contents: read id-token: write concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: build: timeout-minutes: 30 runs-on: latchkey-small strategy: matrix: node-version: [24] steps: - uses: actions/checkout@v4 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v4 with: node-version: ${{ matrix.node-version }} registry-url: 'https://registry.npmjs.org' cache: 'npm' - name: Install dependencies run: npm install - name: Test run: npm test - name: Resolve release metadata run: | if [ "${{ github.event_name }}" = "release" ]; then echo "RELEASE_KIND=release" >> $GITHUB_ENV echo "RELEASE_CHANNEL=$(npm run release-channel --silent)" >> $GITHUB_ENV else echo "RELEASE_KIND=insiders" >> $GITHUB_ENV echo "INSIDERS_VERSION=0.0.0-insiders.$(git rev-parse --short HEAD)" >> $GITHUB_ENV echo "RELEASE_CHANNEL=insiders" >> $GITHUB_ENV fi - name: Version based on commit if: env.RELEASE_KIND == 'insiders' run: npm version "$INSIDERS_VERSION" --force --no-git-tag-version - name: Publish run: npm publish --provenance --tag "$RELEASE_CHANNEL"
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.
- 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 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.