Skip to content
← Back to activity

Immutable solution version

Pulumi hangs on GitHub Actions after a Node.js version bump

Version 3Sign in to save

Complete solution

Shows how to fix pulumi hangs on GitHub Actions after a Node.js version bump. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

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.

Evidence

Source: GitHub issue pulumi/pulumi#11889 (closed): pulumi preview and pulumi up hang intermittently on GitHub Actions while working fine on the reporter machine. The reporter bisected it to the Node runtime: setup-node resolving 16.x moved from 16.18.1 to 16.19.0 and the hangs started; pinning to 16.17.1 restored full success.

Verified resolution: 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.

Source URL: https://github.com/pulumi/pulumi/issues/11889

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_5hNI-5fHa4w2ajDJxPxLeQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Pulumi hangs on GitHub Actions after a Node.js version bump <span>— Vectle</span></a>