Publish npm package workflow (avibe-bot/avibe)

The Publish npm package workflow from avibe-bot/avibe, explained and optimized by Latchkey.

What it does

This is the Publish npm package workflow from the avibe-bot/avibe 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: Publish npm package

on:
  workflow_dispatch:
    inputs:
      ref:
        description: "Git ref to publish from"
        required: true
        default: "master"
        type: string

permissions:
  contents: read
  id-token: write

jobs:
  publish:
    runs-on: ubuntu-latest
    environment: npm
    steps:
      - name: Checkout
        uses: actions/checkout@v5
        with:
          ref: ${{ inputs.ref }}

      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          node-version: "22.14.0"
          registry-url: "https://registry.npmjs.org"

      - name: Install npm with trusted publishing support
        run: npm install -g npm@latest

      - name: Test npm entrypoint
        working-directory: npm/avibe
        run: npm test

      - name: Publish @avibe/cli
        working-directory: npm/avibe
        run: npm publish --access public

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: Publish npm package
 
on:
  workflow_dispatch:
    inputs:
      ref:
        description: "Git ref to publish from"
        required: true
        default: "master"
        type: string
 
permissions:
  contents: read
  id-token: write
 
jobs:
  publish:
    timeout-minutes: 30
    runs-on: latchkey-small
    environment: npm
    steps:
      - name: Checkout
        uses: actions/checkout@v5
        with:
          ref: ${{ inputs.ref }}
 
      - name: Setup Node.js
        uses: actions/setup-node@v5
        with:
          cache: 'npm'
          node-version: "22.14.0"
          registry-url: "https://registry.npmjs.org"
 
      - name: Install npm with trusted publishing support
        run: npm install -g npm@latest
 
      - name: Test npm entrypoint
        working-directory: npm/avibe
        run: npm test
 
      - name: Publish @avibe/cli
        working-directory: npm/avibe
        run: npm publish --access public
 

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.

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