Update dependencies workflow (sigma67/ytmusicapi)

The Update dependencies workflow from sigma67/ytmusicapi, explained and optimized by Latchkey.

What it does

This is the Update dependencies workflow from the sigma67/ytmusicapi 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: Update dependencies

on:
  schedule:
    - cron: "5 3 1 * *"

permissions:
  contents: read

jobs:
  update-dependencies:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - name: Update dependencies
        uses: pdm-project/update-deps-action@main

The same workflow, on Latchkey

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

name: Update dependencies
 
on:
  schedule:
    - cron: "5 3 1 * *"
 
permissions:
  contents: read
 
jobs:
  update-dependencies:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v7
 
      - name: Update dependencies
        uses: pdm-project/update-deps-action@main
 

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.

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