Skip to content

Unpin Node from 24.15.0, restore 24.x#9450

Open
hl662 wants to merge 1 commit into
masterfrom
hl662-hl662-unpin-node-24-version
Open

Unpin Node from 24.15.0, restore 24.x#9450
hl662 wants to merge 1 commit into
masterfrom
hl662-hl662-unpin-node-24-version

Conversation

@hl662

@hl662 hl662 commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

TL;DR

Node 24.16.0 broke Electron's first-launch setup in CI — a callback in yauzl@2.x (used by extract-zip, used by @electron/get) silently stopped firing, leaving no path.txt and failing all Electron-dependent jobs. We pinned every pipeline to 24.15.0 as a stopgap. The upstream Node.js bug (nodejs/node#63487) is now closed, the latest version of Node 24 will pass the postinstall script.

This PR restores the 24.x floating specifier across all Azure Pipelines and GitHub Actions configs.

Closes #9325.

What

Asset Why it exists
Azure Pipelines YAML files (config) The 24.15.0 exact pins blocked CI from picking up newer Node 24 releases; restoring 24.x lets the pipelines track the latest patch.
GitHub Actions YAML files (config) Same pin existed in GH Actions workflows and the shared rush-setup action default; all restored to 24.x for consistency.

Nambot 🤖 (powered by Claude Sonnet 4.6)

Node.js issue nodejs/node#63487 (extract-zip hang on 24.16.0) is now
closed. Remove the temporary pin across all Azure Pipelines and
GitHub Actions configs.

Fixes #9325

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@hl662 hl662 marked this pull request as ready for review June 29, 2026 15:55
@hl662

hl662 commented Jun 29, 2026

Copy link
Copy Markdown
Contributor Author

Holding off till actions/runner-images#14307, it updates 24.x latest to resolve to 24.18.0, will prolly be merged within this week. Then our GH actions CI will be good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Investigate Azure CI regressions on Node 24.16.0 and remove the temporary 24.15.0 pin

2 participants