Release workflow (react-dropzone/react-dropzone)

The Release workflow from react-dropzone/react-dropzone, explained and optimized by Latchkey.

What it does

This is the Release workflow from the react-dropzone/react-dropzone 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

permissions:
  id-token: write  # Required for OIDC/provenance
  contents: write  # Required for creating releases and committing CHANGELOG
  issues: write    # Required for creating release comments
  pull-requests: write  # Required for commenting on PRs

jobs:
  release:
    name: release
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0  # Required for semantic-release to determine version from commits
      - uses: actions/setup-node@v4
        with:
          node-version: 22
          registry-url: https://registry.npmjs.org
      - run: yarn install --pure-lockfile
      - run: yarn build
      - run: npx semantic-release
        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
on:
  push:
    branches:
      - master
 
permissions:
  id-token: write  # Required for OIDC/provenance
  contents: write  # Required for creating releases and committing CHANGELOG
  issues: write    # Required for creating release comments
  pull-requests: write  # Required for commenting on PRs
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  release:
    timeout-minutes: 30
    name: release
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
        with:
          fetch-depth: 0  # Required for semantic-release to determine version from commits
      - uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: 22
          registry-url: https://registry.npmjs.org
      - run: yarn install --pure-lockfile
      - run: yarn build
      - run: npx semantic-release
        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 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 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