HACS/Hassfest validation workflow (cdpuk/ha-bestway)

The HACS/Hassfest validation workflow from cdpuk/ha-bestway, explained and optimized by Latchkey.

What it does

This is the HACS/Hassfest validation workflow from the cdpuk/ha-bestway 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: HACS/Hassfest validation

on:
  pull_request:
  push:
    branches: [main]
  schedule:
    - cron: "0 0 * * *"

jobs:
  validate:
    runs-on: ubuntu-latest
    name: Validate
    steps:
      - uses: actions/checkout@v4

      - name: HACS validation
        uses: hacs/action@main
        with:
          category: integration
          ignore: brands

      - name: Hassfest validation
        uses: home-assistant/actions/hassfest@master

The same workflow, on Latchkey

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

---
name: HACS/Hassfest validation
 
on:
  pull_request:
  push:
    branches: [main]
  schedule:
    - cron: "0 0 * * *"
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  validate:
    timeout-minutes: 30
    runs-on: latchkey-small
    name: Validate
    steps:
      - uses: actions/checkout@v4
 
      - name: HACS validation
        uses: hacs/action@main
        with:
          category: integration
          ignore: brands
 
      - name: Hassfest validation
        uses: home-assistant/actions/hassfest@master
 

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