notify-release workflow (clinicjs/node-clinic)

The notify-release workflow from clinicjs/node-clinic, explained and optimized by Latchkey.

What it does

This is the notify-release workflow from the clinicjs/node-clinic 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:
  workflow_dispatch:
  schedule:
    - cron: '30 8 * * *'

jobs:
  setup:
    runs-on: ubuntu-latest

    steps:
      - name: Notify release

        uses: nearform/github-action-notify-release@v1

        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}

The same workflow, on Latchkey

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

name: notify-release

on:

  workflow_dispatch:

  schedule:

    - cron: '30 8 * * *'

jobs:

  setup:

    timeout-minutes: 30

    runs-on: latchkey-small

    steps:

      - name: Notify release

        uses: nearform/github-action-notify-release@v1

        with:

          github-token: ${{ secrets.GITHUB_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.
• Add a job timeout so a hung step cannot burn hours of runner time.

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.

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