Skip to content
Latchkey

release-docs workflow (viarotel-org/escrcpy)

The release-docs workflow from viarotel-org/escrcpy, explained and optimized by Latchkey.

F

CI health: F - at risk

Point runs-on at Latchkey and get caching, run de-duplication, job timeouts, SHA-pinned actions, self-healing for flaky steps, and up to 58% lower cost, applied automatically.

Grade your own workflow free or run it on Latchkey →
Source: viarotel-org/escrcpy.github/workflows/release-docs.ymlLicense Apache-2.0View source

What it does

This is the release-docs workflow from the viarotel-org/escrcpy repository, a real project running GitHub Actions. It is shown here with attribution under its Apache-2.0 license.

Below, Latchkey shows a faster, safer version produced by its optimization engine.

The workflow

workflow (.yml)
name: release-docs

on:
  push:
    branches:
      - main

permissions:
  contents: write

jobs:
  build-and-deploy:
    concurrency: ci-${{ github.ref }} # Recommended if you intend to make multiple deployments in quick succession.
    runs-on: ubuntu-latest
    steps:
      - name: Check out Git repository
        uses: actions/checkout@v6

      - name: Install Node.js
        uses: actions/setup-node@v6
        with:
          node-version: 24

      - name: Enable corepack and pnpm
        run: |
          corepack enable
          corepack prepare pnpm@10.29.2 --activate

      - name: Install and Build
        run: |
          pnpm install
          pnpm docs:build

      - name: Deploy 🚀
        uses: JamesIves/github-pages-deploy-action@v4
        with:
          branch: docs
          folder: dist-docs

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: release-docs
 
on:
  push:
    branches:
      - main
 
permissions:
  contents: write
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  build-and-deploy:
    timeout-minutes: 30
    concurrency: ci-${{ github.ref }} # Recommended if you intend to make multiple deployments in quick succession.
    runs-on: latchkey-small
    steps:
      - name: Check out Git repository
        uses: actions/checkout@v6
 
      - name: Install Node.js
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 24
 
      - name: Enable corepack and pnpm
        run: |
          corepack enable
          corepack prepare pnpm@10.29.2 --activate
 
      - name: Install and Build
        run: |
          pnpm install
          pnpm docs:build
 
      - name: Deploy 🚀
        uses: JamesIves/github-pages-deploy-action@v4
        with:
          branch: docs
          folder: dist-docs

What changed

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:

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