ci(config): pin verify-docs harness tests to node 20 (#2178)#2193
Merged
Conversation
Node 22's test-runner workers on Linuxbrew return spawn ENOENT on every absolute path, which previously forced the harness step to soft-fail and silently green regressions. Pin the harness unit tests to Node 20; Node 22 is restored for the main content gate (Verify v4 docs) and the guides build. Keeping continue-on-error: true on the harness step for now — with Node 20 the spawns work, which surfaces 7 pre-existing tutorial-driver failures (blog-tutorial fixture's lucee.json is no longer emitted by `wheels new`). Follow-up issue will fix the fixture; once fixed, drop continue-on-error so regressions fail CI as originally intended. Refs #2178 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
bpamiri
force-pushed
the
peter/fix-2178-node20-harness
branch
from
April 22, 2026 04:35
0a81476 to
79a0b3f
Compare
bpamiri
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Pin the verify-docs harness unit tests to Node 20 to work around the Node 22 spawn ENOENT bug documented in #2178 (
child_process.spawnENOENT on every absolute path insidenode --testworker contexts on Linuxbrew). Node 22 is restored for the main content gate (Verify v4 docs) and the guides build.Scope: workflow-only (
.github/workflows/docs-verify.yml). Adds a Node 20 setup step scoped to the harness test, then restores Node 22 before the subsequent steps.Partial fix for #2178
The originally-planned drop of
continue-on-error: trueis kept in place for now. With Node 20 the spawns work, which immediately surfaces 7 pre-existing tutorial-driver failures (theblog-tutorialfixture'slucee.jsonis no longer emitted bywheels new). That's filed as #2196 and will dropcontinue-on-erroronce the fixture is fixed.So this PR changes #2178 from "silently greens regressions via soft-fail" to "reliable spawns + still soft-fail, but the real bug is now visible in CI logs and tracked separately." Concrete step forward without blocking on the fixture bug.
Test plan
verify-docsworkflow runs the harness step on Node 20 and the content gate on Node 22ci(config)scope per CLAUDE.md + recent precedent)Refs #2178
Opens #2196
🤖 Generated with Claude Code