npm publish workflow (jerryc127/hexo-theme-butterfly)

The npm publish workflow from jerryc127/hexo-theme-butterfly, explained and optimized by Latchkey.

What it does

This is the npm publish workflow from the jerryc127/hexo-theme-butterfly repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

name: npm publish


on:
  release:
    types: [created]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v4

    # Setup .npmrc file to publish to npm

    - uses: actions/setup-node@v4

      with:
        node-version: '20.x'

        registry-url: 'https://registry.npmjs.org'

    - run: npm install

    - run: npm publish

      env:
        NODE_AUTH_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: npm publish



on:

  release:

    types: [created]

jobs:

  build:

    timeout-minutes: 30

    runs-on: latchkey-small

    steps:

    - uses: actions/checkout@v4

    # Setup .npmrc file to publish to npm

    - uses: actions/setup-node@v4

      with:

        cache: 'npm'

        node-version: '20.x'

        registry-url: 'https://registry.npmjs.org'

    - run: npm install

    - run: npm publish

      env:

        NODE_AUTH_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.

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