Skip to content
Latchkey

Continuous Releases workflow (nksaraf/vinxi)

The Continuous Releases workflow from nksaraf/vinxi, explained and optimized by Latchkey.

C

CI health: C - fair

Point runs-on at Latchkey and get run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: nksaraf/vinxi.github/workflows/cr.ymlLicense MITView source

What it does

This is the Continuous Releases workflow from the nksaraf/vinxi 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

workflow (.yml)
name: Continuous Releases

on:
  push:
    branches:
      - main
      - dev
      - release-*
    tags-ignore:
      - v*
    paths-ignore:
      - "examples/**"
      - "**/README.md"
  pull_request:
    paths-ignore:
      - "examples/**"
      - "**/README.md"

jobs:
  cr:
    runs-on: ubuntu-22.04

    steps:
      - uses: actions/checkout@v2

      - uses: pnpm/action-setup@v4

      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}
          cache: "pnpm"
      - name: Install dependencies
        run: pnpm install --frozen-lockfile

      - name: Build start
        run: pnpm run build && pnpm run types

      - name: Release
        run: pnpm dlx pkg-pr-new@0.0 publish './packages/*' --template './examples/*' --compact

The same workflow, on Latchkey

Removes redundant runs and caps runaway jobs. Added and changed lines are highlighted.

name: Continuous Releases
 
on:
  push:
    branches:
      - main
      - dev
      - release-*
    tags-ignore:
      - v*
    paths-ignore:
      - "examples/**"
      - "**/README.md"
  pull_request:
    paths-ignore:
      - "examples/**"
      - "**/README.md"
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  cr:
    timeout-minutes: 30
    runs-on: latchkey-small
 
    steps:
      - uses: actions/checkout@v2
 
      - uses: pnpm/action-setup@v4
 
      - name: Use Node.js ${{ matrix.node-version }}
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}
          cache: "pnpm"
      - name: Install dependencies
        run: pnpm install --frozen-lockfile
 
      - name: Build start
        run: pnpm run build && pnpm run types
 
      - name: Release
        run: pnpm dlx pkg-pr-new@0.0 publish './packages/*' --template './examples/*' --compact
 

What changed

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:

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