Version and Release workflow (redux-utilities/redux-actions)

The Version and Release workflow from redux-utilities/redux-actions, explained and optimized by Latchkey.

What it does

This is the Version and Release workflow from the redux-utilities/redux-actions 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: Version and Release

on:
  workflow_dispatch:
    inputs:
      newversion:
        description: 'Version'
        required: true

concurrency:
  group: npm-bump
  cancel-in-progress: true

jobs:
  version_and_release:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3
      with:
        fetch-depth: 0

    - uses: actions/setup-node@v3
      with:
        node-version: 20
        registry-url: 'https://registry.npmjs.org'

    - uses: pnpm/action-setup@v2
      id: pnpm-install
      with:
        version: 8

    - run: pnpm install

    - run: pnpm test

    - uses: bcomnes/npm-bump@v2
      with:
        git_email: github-actions@github.com
        git_username: github-actions
        newversion: ${{ github.event.inputs.newversion }}
        push_version_commit: true
        github_token: ${{ secrets.GITHUB_TOKEN }}
        npm_token: ${{ secrets.NPM_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: Version and Release
 
on:
  workflow_dispatch:
    inputs:
      newversion:
        description: 'Version'
        required: true
 
concurrency:
  group: npm-bump
  cancel-in-progress: true
 
jobs:
  version_and_release:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
    - uses: actions/checkout@v3
      with:
        fetch-depth: 0
 
    - uses: actions/setup-node@v3
      with:
        cache: 'npm'
        node-version: 20
        registry-url: 'https://registry.npmjs.org'
 
    - uses: pnpm/action-setup@v2
      id: pnpm-install
      with:
        version: 8
 
    - run: pnpm install
 
    - run: pnpm test
 
    - uses: bcomnes/npm-bump@v2
      with:
        git_email: github-actions@github.com
        git_username: github-actions
        newversion: ${{ github.event.inputs.newversion }}
        push_version_commit: true
        github_token: ${{ secrets.GITHUB_TOKEN }}
        npm_token: ${{ secrets.NPM_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.
• 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.

Actions used in this workflow