Nightly MagicMirror Package Download Check workflow (Bee-Mar/mmpm)

The Nightly MagicMirror Package Download Check workflow from Bee-Mar/mmpm, explained and optimized by Latchkey.

What it does

This is the Nightly MagicMirror Package Download Check workflow from the Bee-Mar/mmpm 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: Nightly MagicMirror Package Download Check

on:
  schedule:
    - cron: "0 0 * * *" # midnight, every night

jobs:
  test-mmpm-nightly:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        python-version:
          - "3.10"
          - "3.11"
          - "3.12"
          - "3.13"
          - "3.14"
    steps:
      - name: "Test MMPM download"
        run: |
          python -m pip install mmpm

          mmpm list --all # just to see the stdout...doing it twice is a bit wasteful, but it's fine
          mmpm list --all > database.dump

          exit_code=0

          if grep -q "breaking change on the MagicMirror 3rd Party Modules wiki" database.dump; then
              exit_code=1
          fi

          rm database.dump
          exit $exit_code

The same workflow, on Latchkey

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

name: Nightly MagicMirror Package Download Check
 
on:
  schedule:
    - cron: "0 0 * * *" # midnight, every night
 
jobs:
  test-mmpm-nightly:
    timeout-minutes: 30
    runs-on: latchkey-small
    strategy:
      matrix:
        python-version:
          - "3.10"
          - "3.11"
          - "3.12"
          - "3.13"
          - "3.14"
    steps:
      - name: "Test MMPM download"
        run: |
          python -m pip install mmpm
 
          mmpm list --all # just to see the stdout...doing it twice is a bit wasteful, but it's fine
          mmpm list --all > database.dump
 
          exit_code=0
 
          if grep -q "breaking change on the MagicMirror 3rd Party Modules wiki" database.dump; then
              exit_code=1
          fi
 
          rm database.dump
          exit $exit_code
 

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.

What Latchkey heals here

This workflow has steps that commonly fail on transient issues (network, registries, flaky browsers). On Latchkey managed runners they are detected, retried, and self-healed instead of failing your build:

• Dependency installs

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