Deploy Images to GHCR staging workflow (firecrawl/firecrawl-mcp-server)

The Deploy Images to GHCR staging workflow from firecrawl/firecrawl-mcp-server, explained and optimized by Latchkey.

What it does

This is the Deploy Images to GHCR staging workflow from the firecrawl/firecrawl-mcp-server 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 Images to GHCR staging

env:
  DOTNET_VERSION: '6.0.x'

on:
  push:
    branches:
      - staging
      - fastmcp
  workflow_dispatch:


jobs:
  push-image:
    runs-on: ubuntu-latest
    steps:

      - name: 'Checkout GitHub Action'
        uses: actions/checkout@main

      - name: 'Login to GitHub Container Registry'
        uses: docker/login-action@v1
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: 'Set up Docker Buildx'
        uses: docker/setup-buildx-action@v1

      - name: 'Build Service Image'
        uses: docker/build-push-action@v2
        with:
          context: .
          file: ./Dockerfile.service
          push: true
          tags: ghcr.io/firecrawl/firecrawl-mcp-server-alpha:latest
          cache-from: type=registry,ref=ghcr.io/firecrawl/firecrawl-mcp-server-alpha:latest
          cache-to: type=inline

The same workflow, on Latchkey

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

name: Deploy Images to GHCR staging
 
env:
  DOTNET_VERSION: '6.0.x'
 
on:
  push:
    branches:
      - staging
      - fastmcp
  workflow_dispatch:
 
 
concurrency:
  group: ${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true
 
jobs:
  push-image:
    timeout-minutes: 30
    runs-on: latchkey-small
    steps:
 
      - name: 'Checkout GitHub Action'
        uses: actions/checkout@main
 
      - name: 'Login to GitHub Container Registry'
        uses: docker/login-action@v1
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}
 
      - name: 'Set up Docker Buildx'
        uses: docker/setup-buildx-action@v1
 
      - name: 'Build Service Image'
        uses: docker/build-push-action@v2
        with:
          context: .
          file: ./Dockerfile.service
          push: true
          tags: ghcr.io/firecrawl/firecrawl-mcp-server-alpha:latest
          cache-from: type=registry,ref=ghcr.io/firecrawl/firecrawl-mcp-server-alpha:latest
          cache-to: type=inline
 

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.
• Cancel superseded runs when a branch or PR gets a newer push.
• Add a job timeout so a hung step cannot burn hours of runner time.

3 third-party actions are referenced by a movable tag. Pin them 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:

• Container pulls and builds

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