Delete Stale Spaces workflow (gradio-app/gradio)

The Delete Stale Spaces workflow from gradio-app/gradio, explained and optimized by Latchkey.

What it does

This is the Delete Stale Spaces workflow from the gradio-app/gradio 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

# safe runs from main

name: Delete Stale Spaces

on:
  schedule:
    - cron: "0 0 * * *"
  workflow_dispatch:
    inputs:
      daysStale:
        description: "How stale a space needs to be to be deleted (days)"
        required: true
        default: "7"

permissions: {}

jobs:
  delete-old-spaces:
    permissions:
      contents: read
    environment: deploy_spaces
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install Python
        uses: actions/setup-python@v5
        with:
          python-version: "3.12"
      - name: Install pip
        run: python -m pip install pip wheel requests
      - name: Install Hub Client Library
        run: pip install huggingface-hub==0.9.1
      - name: Set daysStale
        env:
          DEFAULT_DAYS_STALE: "7"
          DAYS_STALE: ${{ github.event.inputs.daysStale  || env.DEFAULT_DAYS_STALE}}
        run: echo DAYS_STALE=  "$DAYS_STALE"  >> $GITHUB_ENV
      - name: Find and delete stale spaces
        run: |
          python scripts/delete_old_spaces.py $DAYS_STALE \
          gradio-pr-deploys \
          ${{ secrets.WEBSITE_SPACES_DEPLOY_TOKEN }}

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.

# safe runs from main
 
name: Delete Stale Spaces
 
on:
  schedule:
    - cron: "0 0 * * *"
  workflow_dispatch:
    inputs:
      daysStale:
        description: "How stale a space needs to be to be deleted (days)"
        required: true
        default: "7"
 
permissions: {}
 
jobs:
  delete-old-spaces:
    timeout-minutes: 30
    permissions:
      contents: read
    environment: deploy_spaces
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
      - name: Install Python
        uses: actions/setup-python@v5
        with:
          cache: 'pip'
          python-version: "3.12"
      - name: Install pip
        run: python -m pip install pip wheel requests
      - name: Install Hub Client Library
        run: pip install huggingface-hub==0.9.1
      - name: Set daysStale
        env:
          DEFAULT_DAYS_STALE: "7"
          DAYS_STALE: ${{ github.event.inputs.daysStale  || env.DEFAULT_DAYS_STALE}}
        run: echo DAYS_STALE=  "$DAYS_STALE"  >> $GITHUB_ENV
      - name: Find and delete stale spaces
        run: |
          python scripts/delete_old_spaces.py $DAYS_STALE \
          gradio-pr-deploys \
          ${{ secrets.WEBSITE_SPACES_DEPLOY_TOKEN }}
 

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

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