v22.5.1 proposal

[richardlau]

2024-07-19, Version 22.5.1 (Current), @richardlau

Notable Changes

This release fixes a regression introduced in Node.js 22.5.0. The problem is known to display the following symptoms:

• Crash with FATAL ERROR: v8::Object::GetCreationContextChecked No creation context available #53902
• npm errors with npm error Exit handler never called! npm/cli#7657
• yarn hangs or outputs Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation) yarnpkg/berry#6398

Commits

• [e2deeedc6e] - Revert "fs: add v8 fast api to closeSync" (Aviv Keller) #53904

---

cc @nodejs/releasers

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/60436/
CITGM: https://ci.nodejs.org/job/citgm-smoker/3461/
Release build with fd9233a: https://ci-release.nodejs.org/job/iojs+release/10361/

[merceyz]

yarn hangs or outputs Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation) yarnpkg/berry#6398

The Yarn symptom is that it either hangs or if not in interactive mode (CI=true) terminates mid install with exit code 0 (empty event loop) which causes commands run after that to complain that a install hasn't been done.

[richardlau]

yarn hangs or outputs Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation) yarnpkg/berry#6398

The Yarn symptom is that it either hangs or if not in interactive mode (CI=true) terminates mid install with exit code 0 (empty event loop) which causes commands run after that to complain that a install hasn't been done.

ah thanks. If I update the wording I'm going to have to rerun the builds. I'm doing some final checks -- if anything comes up and the build needs to change I'll reword otherwise I think we can release as-is and reword afterwards in follow up PRs to the changelog if necessary.

[richardlau]

CITGM: https://ci.nodejs.org/job/citgm-smoker/3461/

For some reason, the CITGM job installed [email protected] instead of the latest [email protected]. It wasn't just this job -- the previous jobs appear to have done the same. Some of the failing modules are ones that have been removed from the lookup since 8.1.0 (e.g. bluebird).
e.g. https://ci.nodejs.org/job/citgm-smoker/3461/nodes=ubuntu2204-64/consoleFull

03:06:31 npm verbose title npm install citgm
03:06:31 npm verbose argv "install" "--prefix" "/home/iojs/build/workspace/citgm-smoker/smoker" "--global" "--loglevel" "silly" "citgm"
03:06:31 npm verbose logfile logs-max:10 dir:/home/iojs/build/workspace/citgm-smoker/npm_cache/_logs/2024-07-19T02_06_31_144Z-
03:06:31 npm verbose logfile /home/iojs/build/workspace/citgm-smoker/npm_cache/_logs/2024-07-19T02_06_31_144Z-debug-0.log
03:06:31 npm silly packumentCache heap:2090074112 maxSize:522518528 maxEntrySize:261259264
03:06:31 npm silly logfile start cleaning logs, removing 2 files
03:06:31 npm silly idealTree buildDeps
03:06:31 npm silly fetch manifest citgm@*
03:06:31 npm silly packumentCache full:https://registry.npmjs.org/citgm cache-miss
03:06:31 npm silly logfile done cleaning log files
03:06:31 npm http fetch GET 200 https://registry.npmjs.org/citgm 200ms (cache revalidated)
03:06:31 npm silly packumentCache full:https://registry.npmjs.org/citgm set size:879187 disposed:false
03:06:31 npm silly placeDep ROOT [email protected] OK for:  want: *