Review Dependencies workflow (MagicMirrorOrg/MagicMirror)

The Review Dependencies workflow from MagicMirrorOrg/MagicMirror, explained and optimized by Latchkey.

What it does

This is the Review Dependencies workflow from the MagicMirrorOrg/MagicMirror 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

# This workflow scans your pull requests for dependency changes, and will raise an error if any vulnerabilities or invalid licenses are being introduced.
# For more information see: https://github.com/actions/dependency-review-action

name: "Review Dependencies"

on: [pull_request]

permissions:
  contents: read

jobs:
  dependency-review:
    runs-on: ubuntu-slim
    steps:
      - name: "Checkout code"
        uses: actions/checkout@v7
      - name: "Dependency Review"
        uses: actions/dependency-review-action@v5

The same workflow, on Latchkey

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

# This workflow scans your pull requests for dependency changes, and will raise an error if any vulnerabilities or invalid licenses are being introduced.
# For more information see: https://github.com/actions/dependency-review-action
 
name: "Review Dependencies"
 
on: [pull_request]
 
permissions:
  contents: read
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  dependency-review:
    timeout-minutes: 30
    runs-on: ubuntu-slim
    steps:
      - name: "Checkout code"
        uses: actions/checkout@v7
      - name: "Dependency Review"
        uses: actions/dependency-review-action@v5
 

What changed

• 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.

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