$ the-wire · showcase
gyp-next raises CMake floor to 3.10, node trims flaky test list
By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology
3 people shipped this
gyp-next's generated CMake files broke on CMake 4.0+, and the fix lands as a breaking change, while node's flaky-test ledger gets cleaned up after months of underlying fixes.
fix!(cmake): require CMake 3.10 and quote custom command comments (#361) nodejs/gyp-next
The CMake generator's output no longer builds on current CMake: cmake_minimum_required(VERSION 2.8.8) is a hard error on CMake 4.0+, which dropped compatibility with versions below 3.5, and CMake 3.31+ warns for anything under 3.10. Generated projects now require 3.10, and COMMENT values for actions, rules and copies are quoted so messages like "Checking inspector protocol compatibility" stop b...
fix!(cmake): require CMake 3.10 and quote custom command comments nodejs/gyp-next
The pull request spells out the two failure modes: unless -DCMAKE_POLICY_VERSION_MINIMUM=3.5 is passed, the old policy version is rejected outright, and unquoted COMMENT text warns on CMake 3.31+ before becoming an error. Requiring 3.10 also sets the policy version implicitly, so the separate cmake_policy() call is gone from the generated output.
test: remove stale flaky status entries nodejs/node
Filip Skokan removed flaky-status entries for test-performance-function and test-report-fatal-error, both of which had been renamed, so the old entries matched nothing. The cleanup matters because stale entries silently stop suppressing anything they were meant to suppress.
test: unmark test-cpu-prof-dir-worker as flaky nodejs/node
test-cpu-prof-dir-worker loses its flaky marking: the non-Windows workload rose from fib(30) to fib(40) and Profiler.setSamplingInterval moved ahead of Profiler.start so the requested interval actually takes effect, which closed the gap where the test could finish without recording a workload frame.
test: unmark exit timeout tests as flaky nodejs/node
test-http2-large-file and test-fs-read-stream-concurrent-reads are also unmarked flaky, following a fix that limits the exit-time DrainTasks wait to user-blocking tasks, removing the deadlock between the compiler task and main-thread garbage collection. Together with stale SEA Linux debug entries, it is one cleanup effort: expectations retired because the underlying behavior changed.
build(deps-dev): bump eslint to 10 and neostandard to 0.14.0-next.1 (#3374) nodejs/node-gyp
node-gyp bumps eslint to 10 and neostandard to 0.14.0-next.1 together, because neostandard 0.13.0 declared peer eslint@^9.0.0 and an eslint-only bump made npm install fail with ERESOLVE across every CI job, not just linting. The new prerelease widens the peer range to ^9.22.0 || ^10.0.0, keeping the blast radius inside the lint job.
Action items
