release-please workflow (Mause/duckdb_engine)

The release-please workflow from Mause/duckdb_engine, explained and optimized by Latchkey.

What it does

This is the release-please workflow from the Mause/duckdb_engine 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

on:
  push:
    branches:
      - main
  workflow_dispatch:

name: release-please
jobs:
  release-please:
    runs-on: ubuntu-latest
    steps:
      - run: npx release-please debug-config --repo-url https://github.com/Mause/duckdb_engine
      - uses: googleapis/release-please-action@v4
        with:
          release-type: python
          token: ${{ secrets.ACCESS_TOKEN }}

The same workflow, on Latchkey

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

on:
  push:
    branches:
      - main
  workflow_dispatch:
 
name: release-please
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  release-please:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - run: npx release-please debug-config --repo-url https://github.com/Mause/duckdb_engine
      - uses: googleapis/release-please-action@v4
        with:
          release-type: python
          token: ${{ secrets.ACCESS_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.

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.

Actions used in this workflow