Deploy to KeyCDN (Dev) workflow (olton/metroui)

The Deploy to KeyCDN (Dev) workflow from olton/metroui, explained and optimized by Latchkey.

What it does

This is the Deploy to KeyCDN (Dev) workflow from the olton/metroui 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: Deploy to KeyCDN (Dev)
on:
  push:
    branches:
      - dev
    paths:
      - 'source/**/*.js'
      - 'source/**/*.css'
      - 'source/**/*.less'
jobs:
  build:
    name: Build
    runs-on: windows-latest
    steps:
      - uses: actions/setup-node@v4
        with:
          node-version: 22

      - name: Checkout code
        uses: actions/checkout@v4
        with:
          ref: dev

      - name: Install dependencies
        run: npm install

      - name: Build
        run: npm run build

      - name: Push files
        uses: SamKirkland/FTP-Deploy-Action@v4.3.4
        with:
          server: ftp.keycdn.com
          username: metro4
          password: ${{ secrets.FTP_PASSWORD_KEYCDN }}
          dangerous-clean-slate: true
          local-dir: ./lib/
          server-dir: dev/
          

The same workflow, on Latchkey

Estimated ~20% faster on cache hits, plus fewer wasted runs and a safer supply chain. Added and changed lines are highlighted.

name: Deploy to KeyCDN (Dev)
on:
  push:
    branches:
      - dev
    paths:
      - 'source/**/*.js'
      - 'source/**/*.css'
      - 'source/**/*.less'
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build:
    timeout-minutes: 30
    name: Build
    runs-on: windows-latest
    steps:
      - uses: actions/setup-node@v4
        with:
          cache: 'npm'
          node-version: 22
 
      - name: Checkout code
        uses: actions/checkout@v4
        with:
          ref: dev
 
      - name: Install dependencies
        run: npm install
 
      - name: Build
        run: npm run build
 
      - name: Push files
        uses: SamKirkland/FTP-Deploy-Action@v4.3.4
        with:
          server: ftp.keycdn.com
          username: metro4
          password: ${{ secrets.FTP_PASSWORD_KEYCDN }}
          dangerous-clean-slate: true
          local-dir: ./lib/
          server-dir: dev/
          

What changed

• Cancel superseded runs when a branch or PR gets a newer push.
• Cache dependency installs on the setup step so they are served from cache.
• 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.

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 per trigger. On Latchkey the same minutes cost up to 58% less than GitHub-hosted, with zero queue time.

Actions used in this workflow