Release workflow (iamkun/dayjs)

The Release workflow from iamkun/dayjs, explained and optimized by Latchkey.

What it does

This is the Release workflow from the iamkun/dayjs 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: [master]

jobs:
  lint-and-test:
    uses: ./.github/workflows/lint-test.yml
    secrets:
      inherit
  release:
    needs: lint-and-test
    runs-on: ubuntu-latest
    permissions:
      contents: write
      issues: write
      pull-requests: write
      id-token: write
    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 'lts/*'
      - name: Install dependencies
        run: npm clean-install
      - name: Build
        env:
          NODE_OPTIONS: --openssl-legacy-provider
        run: npm run build && npm run babel
      - name: Verify provenance
        run: npm audit signatures
      - name: Release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          npm install @semantic-release/changelog @semantic-release/git semantic-release --no-save
          npx patch-package
          npx semantic-release

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
on:
  push:
    branches: [master]
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  lint-and-test:
    timeout-minutes: 30
    uses: ./.github/workflows/lint-test.yml
    secrets:
      inherit
  release:
    timeout-minutes: 30
    needs: lint-and-test
    runs-on: latchkey-small
    permissions:
      contents: write
      issues: write
      pull-requests: write
      id-token: write
    steps:
      - name: Checkout
        uses: actions/checkout@v3
        with:
          fetch-depth: 0
      - name: Setup Node.js
        uses: actions/setup-node@v3
        with:
          cache: 'npm'
          node-version: 'lts/*'
      - name: Install dependencies
        run: npm clean-install
      - name: Build
        env:
          NODE_OPTIONS: --openssl-legacy-provider
        run: npm run build && npm run babel
      - name: Verify provenance
        run: npm audit signatures
      - name: Release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        run: |
          npm install @semantic-release/changelog @semantic-release/git semantic-release --no-save
          npx patch-package
          npx semantic-release
 

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 uses latchkey-small; pick the runner size that fits the job.
• Cancel superseded runs when a branch or PR gets a newer push.
• 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.

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 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow