publish workflow (snapappointments/bootstrap-select)

The publish workflow from snapappointments/bootstrap-select, explained and optimized by Latchkey.

What it does

This is the publish workflow from the snapappointments/bootstrap-select 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
on:
 release:
   types: [published]
jobs:
  publish:
    runs-on: ubuntu-latest
    name: Publish latest release
    steps:
      - uses: actions/checkout@v2
      - name: Setup node
        uses: actions/setup-node@v2
        with:
          node-version: '16.x'
          cache: 'npm'
          registry-url: 'https://registry.npmjs.org'
      - name: Install dependencies
        run: npm ci
      - name: Build package
        run: grunt build
      - name: Publish npm package
        run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
      - name: Publish NuGet package
        id: publish_nuget
        uses: laget-se/publish-nuget@v2
        with:
          NUGET_KEY: ${{ secrets.NUGET_API_KEY }}
          NUSPEC_FILE: nuget/bootstrap-select.nuspec
          PACKAGE_NAME: bootstrap-select
          VERSION_FILE_PATH: nuget/bootstrap-select.nuspec
          VERSION_REGEX: ^\s*<version>(.*)<\/version>\s*$

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
on:
 release:
   types: [published]
jobs:
  publish:
    runs-on: latchkey-small
    name: Publish latest release
    steps:
      - uses: actions/checkout@v2
      - name: Setup node
        uses: actions/setup-node@v2
        with:
         cache: 'npm'
          node-version: '16.x'
          cache: 'npm'
          registry-url: 'https://registry.npmjs.org'
      - name: Install dependencies
        run: npm ci
      - name: Build package
        run: grunt build
      - name: Publish npm package
        run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
      - name: Publish NuGet package
        id: publish_nuget
        uses: laget-se/publish-nuget@v2
        with:
          NUGET_KEY: ${{ secrets.NUGET_API_KEY }}
          NUSPEC_FILE: nuget/bootstrap-select.nuspec
          PACKAGE_NAME: bootstrap-select
          VERSION_FILE_PATH: nuget/bootstrap-select.nuspec
          VERSION_REGEX: ^\s*<version>(.*)<\/version>\s*$
 

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.

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