Publish Package workflow (openlayers/openlayers)

The Publish Package workflow from openlayers/openlayers, explained and optimized by Latchkey.

CI health: D - needs work

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

Grade your own workflow free or run it on Latchkey →

Source: openlayers/openlayers.github/workflows/publish.ymlLicense BSD-2-ClauseView source

What it does

This is the Publish Package workflow from the openlayers/openlayers repository, a real project running GitHub Actions. It is shown here with attribution under its BSD-2-Clause license.

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

The workflow

workflow (.yml)

name: Publish Package

on:
  push:
    branches:
      - main
    tags:
      - 'v*.*.*'

permissions:
  contents: read
  id-token: write

jobs:
  publish-branch:
    if: startsWith(github.ref, 'refs/heads/')
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7.0.0
      - uses: actions/setup-node@v6
        with:
          node-version: '24'
          registry-url: 'https://registry.npmjs.org'
      - name: Install dependencies
        run: npm ci
      - name: Publish
        run: |
          VERSION=$(node tasks/next-dev-version.js)
          npm --no-git-tag-version version ${VERSION}
          npm run build-package
          cd build/ol
          npm publish --tag dev

  publish-tag:
    if: startsWith(github.ref, 'refs/tags/')
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7.0.0
      - uses: actions/setup-node@v6
        with:
          node-version: '24'
          registry-url: 'https://registry.npmjs.org'
      - name: Install dependencies
        run: npm ci
      - name: Assert Latest Release
        run: node tasks/newest-tag.js --tag ${GITHUB_REF_NAME}
      - name: Publish
        run: |
          npm run build-package
          cd build/ol
          npm publish

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 Package
 
on:
  push:
    branches:
      - main
    tags:
      - 'v*.*.*'
 
permissions:
  contents: read
  id-token: write
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  publish-branch:
    timeout-minutes: 30
    if: startsWith(github.ref, 'refs/heads/')
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7.0.0
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: '24'
          registry-url: 'https://registry.npmjs.org'
      - name: Install dependencies
        run: npm ci
      - name: Publish
        run: |
          VERSION=$(node tasks/next-dev-version.js)
          npm --no-git-tag-version version ${VERSION}
          npm run build-package
          cd build/ol
          npm publish --tag dev
 
  publish-tag:
    timeout-minutes: 30
    if: startsWith(github.ref, 'refs/tags/')
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7.0.0
      - uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: '24'
          registry-url: 'https://registry.npmjs.org'
      - name: Install dependencies
        run: npm ci
      - name: Assert Latest Release
        run: node tasks/newest-tag.js --tag ${GITHUB_REF_NAME}
      - name: Publish
        run: |
          npm run build-package
          cd build/ol
          npm publish

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.

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 2 jobs per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow

actions/checkout actions/setup-node