Firefox metadata workflow (ChatGPTBox-dev/chatGPTBox)

The Firefox metadata workflow from ChatGPTBox-dev/chatGPTBox, explained and optimized by Latchkey.

What it does

This is the Firefox metadata workflow from the ChatGPTBox-dev/chatGPTBox 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: Firefox metadata

on:
  workflow_dispatch:
    inputs:
      version:
        description: "Firefox version to update, for example 2.6.1"
        required: true
        type: string

permissions:
  contents: read

jobs:
  update-firefox-metadata:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v7

      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          node-version: 22

      - name: Install dependencies
        run: npm ci

      - name: Update Firefox metadata
        run: npm run release:update-firefox-metadata -- --version "${{ inputs.version }}"
        env:
          FIREFOX_EXTENSION_ID: ${{ secrets.FIREFOX_EXTENSION_ID }}
          FIREFOX_JWT_ISSUER: ${{ secrets.FIREFOX_JWT_ISSUER }}
          FIREFOX_JWT_SECRET: ${{ secrets.FIREFOX_JWT_SECRET }}

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: Firefox metadata
 
on:
  workflow_dispatch:
    inputs:
      version:
        description: "Firefox version to update, for example 2.6.1"
        required: true
        type: string
 
permissions:
  contents: read
 
jobs:
  update-firefox-metadata:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
      - name: Checkout
        uses: actions/checkout@v7
 
      - name: Setup Node.js
        uses: actions/setup-node@v6
        with:
          cache: 'npm'
          node-version: 22
 
      - name: Install dependencies
        run: npm ci
 
      - name: Update Firefox metadata
        run: npm run release:update-firefox-metadata -- --version "${{ inputs.version }}"
        env:
          FIREFOX_EXTENSION_ID: ${{ secrets.FIREFOX_EXTENSION_ID }}
          FIREFOX_JWT_ISSUER: ${{ secrets.FIREFOX_JWT_ISSUER }}
          FIREFOX_JWT_SECRET: ${{ secrets.FIREFOX_JWT_SECRET }}
 

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