Release workflow (chakra-ui/chakra-ui)
The Release workflow from chakra-ui/chakra-ui, explained and optimized by Latchkey.
CI health: B - good
Point runs-on at Latchkey and get job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.
What it does
This is the Release workflow from the chakra-ui/chakra-ui 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:
paths:
- ".changeset/**"
- "packages/**"
branches:
- main
concurrency:
group: ${{ github.workflow }}-${{ github.ref }}
jobs:
tests:
name: Tests
runs-on: ubuntu-latest
steps:
- name: Checkout branch
uses: actions/checkout@v6
- name: Install
uses: ./.github/composite-actions/install
- name: Run tests
run: pnpm test
release:
name: Release
runs-on: ubuntu-latest
steps:
- name: Checkout branch
uses: actions/checkout@v6
with:
fetch-depth: 0
token: ${{ secrets.SAGE_PAT }}
- name: Install
uses: ./.github/composite-actions/install
- name: Build
run: pnpm build
- name: Create release Pull Request or publish to NPM
id: changesets
uses: changesets/action@v1
with:
publish: pnpm release
commit: "ci(changesets): version packages"
setupGitUser: false
env:
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
- name: Slack notification
if: steps.changesets.outputs.published == 'true'
run: pnpm slack
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
The same workflow, on Latchkey
Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.
name: Release on: push: paths: - ".changeset/**" - "packages/**" branches: - main concurrency: group: ${{ github.workflow }}-${{ github.ref }} jobs: tests: timeout-minutes: 30 name: Tests runs-on: latchkey-small steps: - name: Checkout branch uses: actions/checkout@v6 - name: Install uses: ./.github/composite-actions/install - name: Run tests run: pnpm test release: timeout-minutes: 30 name: Release runs-on: latchkey-small steps: - name: Checkout branch uses: actions/checkout@v6 with: fetch-depth: 0 token: ${{ secrets.SAGE_PAT }} - name: Install uses: ./.github/composite-actions/install - name: Build run: pnpm build - name: Create release Pull Request or publish to NPM id: changesets uses: changesets/action@v1 with: publish: pnpm release commit: "ci(changesets): version packages" setupGitUser: false env: NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} NPM_TOKEN: ${{ secrets.NPM_TOKEN }} GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - name: Slack notification if: steps.changesets.outputs.published == 'true' run: pnpm slack env: SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
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. - 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.
This workflow runs 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.