GitHub Actions ubuntu-latest builds fail after runner image rollout without workflow changes

Confirmed Behavior

The ubuntu-latest alias is not a fixed image. GitHub updates it periodically with a newer Ubuntu runner image, changing preinstalled compilers, runtimes, and system tools. This can cause builds to fail on unchanged commits when the runner environment drifts.

Root Cause: Image Drift

When GitHub rolls ubuntu-latest forward, the underlying OS, package versions, and tool locations may change. A build that succeeded yesterday might fail today if:

• A compiler version changes (e.g., gcc or clang)
• A runtime is updated or removed (e.g., node, python)
• System libraries are patched or deprecated

Diagnosis Steps

1. Check runner metadata in workflow logs - Look for Runner OS, Runner Version, and Runner Name fields in the job summary. Compare these between passing and failing runs.
2. Log tool versions explicitly - Add diagnostic steps early in your workflow:

- name: Log environment
  run: |
    echo "Node: $(node --version)"
    echo "Python: $(python3 --version)"
    echo "GCC: $(gcc --version | head -1)"
    echo "Runner OS: ${{ runner.os }}"
    echo "Runner Name: ${{ runner.name }}"

1. Compare outputs - If tool versions differ between runs, the runner image has changed.
2. Review GitHub’s runner image changelog - GitHub announces runner updates in the runner-images releases.

Solution: Pin the Runner Image

To reproduce a specific environment, pin to a fixed runner label instead of ubuntu-latest:

runs-on: ubuntu-22.04  # Fixed LTS release
# or
runs-on: ubuntu-20.04  # Older LTS (if still supported)

This locks the job to a specific Ubuntu version. Note that pinned images may not receive the latest security patches or tool updates.

Alternative: Container-Based Runners

For maximum reproducibility, use a container with a fixed image digest:

jobs:
  build:
    runs-on: ubuntu-latest
    container:
      image: node:18@sha256:abc123...  # Pinned digest

Key Points

• ubuntu-latest resolves to different images over time; there is no way to freeze it to a prior state.
• Pinning to ubuntu-22.04 or using a container with a digest provides reproducibility.
• Diagnose by comparing runner metadata and tool versions across runs.