Create Release workflow (carloscuesta/gitmoji-cli)

The Create Release workflow from carloscuesta/gitmoji-cli, explained and optimized by Latchkey.

What it does

This is the Create Release workflow from the carloscuesta/gitmoji-cli 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

on:
  push:
    tags:
      - 'v*'

name: Create Release

jobs:
  build:
    name: Create Release
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v6
      - uses: actions/setup-node@v6
        with:
          node-version: '20.x'
      - name: Build
        run: |
          yarn install --ignore-scripts
          yarn build
      - name: Publish package to NPM 🚀
        env:
          NPM_TOKEN: ${{ secrets.NPM_AUTOMATION_TOKEN }}
        run: |
         npm config set '//registry.npmjs.org/:_authToken' "${NPM_TOKEN}"
         npm publish
      - name: Package 📦
        run: yarn package
      - name: Publish Release ✨
        uses: softprops/action-gh-release@v3
        with:
          name: gitmoji-cli ${{github.ref_name}}
          generate_release_notes: true
          files: |
            ./bin/gitmoji-linux
            ./bin/gitmoji-macos
            ./bin/gitmoji-win.exe

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.

on:
  push:
    tags:
      - 'v*'
 
name: Create Release
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    name: Create Release
    runs-on: latchkey-small
    steps:
      - name: Checkout
        uses: actions/checkout@v6
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: '20.x'
      - name: Build
        run: |
          yarn install --ignore-scripts
          yarn build
      - name: Publish package to NPM 🚀
        env:
          NPM_TOKEN: ${{ secrets.NPM_AUTOMATION_TOKEN }}
        run: |
         npm config set '//registry.npmjs.org/:_authToken' "${NPM_TOKEN}"
         npm publish
      - name: Package 📦
        run: yarn package
      - name: Publish Release ✨
        uses: softprops/action-gh-release@v3
        with:
          name: gitmoji-cli ${{github.ref_name}}
          generate_release_notes: true
          files: |
            ./bin/gitmoji-linux
            ./bin/gitmoji-macos
            ./bin/gitmoji-win.exe
 

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.

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.

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