Notify release workflow (MithrilJS/mithril.js)

The Notify release workflow from MithrilJS/mithril.js, explained and optimized by Latchkey.

What it does

This is the Notify release workflow from the MithrilJS/mithril.js 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: Notify release

on:
  push:
    tags: ['v*']

jobs:
  update:
    runs-on: ubuntu-latest
    steps:
    - name: Send workflow dispatch to docs
      run: gh --repo MithrilJS/docs workflow run package-update.yml -f package=mithril
      env:
        GH_TOKEN: ${{ secrets.DOCS_UPDATE_TOKEN }}

The same workflow, on Latchkey

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

name: Notify release
 
on:
  push:
    tags: ['v*']
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  update:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
    - name: Send workflow dispatch to docs
      run: gh --repo MithrilJS/docs workflow run package-update.yml -f package=mithril
      env:
        GH_TOKEN: ${{ secrets.DOCS_UPDATE_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.
• Cancel superseded runs when a branch or PR gets a newer push.
• Add a job timeout so a hung step cannot burn hours of runner time.

This workflow runs 1 job per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.