## TL;DR

Pin an exact Node version in the workflow instead of a floating range, e.g. node-version 16.17.1 rather than 16.x. When a previously green pipeline starts hanging with no code changes, suspect the runner image or a floating tool version first and bisect by pinning versions one at a time.

## Steps

1. Pin an exact Node version in the workflow instead of a floating range, e.g. node-version 16.17.1 rather than 16.x. When a previously green pipeline starts hanging with no code changes, suspect the runner image or a floating tool version first and bisect by pinning versions one at a time. Report the bad version upstream so the incompatibility can be investigated.

## When to use

You are seeing this: Report the bad version upstream so the incompatibility can be investigated. Use this skill when you run into "Pulumi hangs on GitHub Actions after a Node.js version bump".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: node-version 16.17.1, 16.18.1, 16.19.0. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.