Question

Your team runs a matrix build across `ubuntu-latest`, `windows-latest`, and `macos-latest`. After a scheduled nightly run, the Linux jobs suddenly fail because GitHub rolled the `ubuntu-latest` label to a newer runner image that ships a different default Node.js version, breaking a native dependency compile. You need the most reliable fix that keeps builds reproducible while still allowing controlled upgrades. Which approach should you take?

Accepted Answer

Pin the Linux matrix entry to a specific runner label such as `ubuntu-22.04` instead of `ubuntu-latest`, and bump the version deliberately when you validate the new image.

Answer

Set `strategy.fail-fast: false` so the other matrix legs continue even when the Linux leg fails, resolving the reproducibility problem.

Answer

Add `continue-on-error: true` to the Linux job so the workflow reports success regardless of the image change.

Answer

Increase `strategy.max-parallel` so the Linux jobs run before GitHub applies the new image, avoiding the version drift.