Release @eidolon-components and @eidolon-client workflow (eidolon-ai/eidolon)
The Release @eidolon-components and @eidolon-client workflow from eidolon-ai/eidolon, explained and optimized by Latchkey.
CI health: C - fair
Point runs-on at Latchkey and get caching, 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 @eidolon-components and @eidolon-client workflow from the eidolon-ai/eidolon repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.
Below, Latchkey shows a faster, safer version produced by its optimization engine.
The workflow
name: Release @eidolon-components and @eidolon-client
on:
push:
branches:
- main
workflow_dispatch:
concurrency: ${{ github.workflow }}-${{ github.ref }}
jobs:
release:
name: Release
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
token: ${{ secrets.GH_PAT }}
fetch-depth: 0
- name: Setup Node.js 20
uses: actions/setup-node@v3
with:
node-version: 20
- uses: pnpm/action-setup@v3
name: Install pnpm
with:
version: 9
run_install: false
- name: Get pnpm store directory
shell: bash
run: |
echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV
- uses: actions/cache@v4
name: Setup pnpm cache
with:
path: ${{ env.STORE_PATH }}
key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }}
restore-keys: |
${{ runner.os }}-pnpm-store-
- name: Install Dependencies
run: pnpm install
working-directory: webui
- name: Build Packages
run: pnpm build
working-directory: webui
- name: Version Packages
run: pnpm changeset version
working-directory: webui
- name: Publish Packages
run: |
pnpm --filter @eidolon-ai/client changeset publish --no-git-checks
pnpm --filter @eidolon-ai/components changeset publish --no-git-checks
working-directory: webui
- name: Push Tags to GitHub
run: git push --follow-tags
working-directory: webui
# todo, we don't have changesets yet
# - name: Create Release Pull Request
# id: changesets
# uses: changesets/action@v1
# env:
# GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}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: Release @eidolon-components and @eidolon-client on: push: branches: - main workflow_dispatch: concurrency: ${{ github.workflow }}-${{ github.ref }} jobs: release: timeout-minutes: 30 name: Release runs-on: latchkey-small steps: - uses: actions/checkout@v4 with: token: ${{ secrets.GH_PAT }} fetch-depth: 0 - name: Setup Node.js 20 uses: actions/setup-node@v3 with: cache: 'npm' node-version: 20 - uses: pnpm/action-setup@v3 name: Install pnpm with: version: 9 run_install: false - name: Get pnpm store directory shell: bash run: | echo "STORE_PATH=$(pnpm store path --silent)" >> $GITHUB_ENV - uses: actions/cache@v4 name: Setup pnpm cache with: path: ${{ env.STORE_PATH }} key: ${{ runner.os }}-pnpm-store-${{ hashFiles('**/pnpm-lock.yaml') }} restore-keys: | ${{ runner.os }}-pnpm-store- - name: Install Dependencies run: pnpm install working-directory: webui - name: Build Packages run: pnpm build working-directory: webui - name: Version Packages run: pnpm changeset version working-directory: webui - name: Publish Packages run: | pnpm --filter @eidolon-ai/client changeset publish --no-git-checks pnpm --filter @eidolon-ai/components changeset publish --no-git-checks working-directory: webui - name: Push Tags to GitHub run: git push --follow-tags working-directory: webui # todo, we don't have changesets yet # - name: Create Release Pull Request # id: changesets # uses: changesets/action@v1 # env: # GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
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. - 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.
2 third-party actions are referenced by a movable tag. Pin them 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 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.