Check version workflow (fastapi-practices/fastapi-best-architecture)

The Check version workflow from fastapi-practices/fastapi-best-architecture, explained and optimized by Latchkey.

What it does

This is the Check version workflow from the fastapi-practices/fastapi-best-architecture 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: Check version

on:
  push:
    tags:
      - v*

jobs:
  check-version:
    name: check version
    runs-on: ubuntu-latest
    if: startsWith(github.ref, 'refs/tags/')
    steps:
      - uses: actions/checkout@v6

      - name: Install uv
        uses: astral-sh/setup-uv@v7

      - name: Set up Python
        run: uv python install 3.13

      - name: Check the package version
        uses: samuelcolvin/check-python-version@v5
        with:
          version_file_path: backend/__init__.py

The same workflow, on Latchkey

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

name: Check version
 
on:
  push:
    tags:
      - v*
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  check-version:
    timeout-minutes: 30
    name: check version
    runs-on: latchkey-small
    if: startsWith(github.ref, 'refs/tags/')
    steps:
      - uses: actions/checkout@v6
 
      - name: Install uv
        uses: astral-sh/setup-uv@v7
 
      - name: Set up Python
        run: uv python install 3.13
 
      - name: Check the package version
        uses: samuelcolvin/check-python-version@v5
        with:
          version_file_path: backend/__init__.py
 

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.

2 third-party actions are referenced by a movable tag. Pin them 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