test(ci): DO NOT MERGE — control experiment for test_node (20) failure - #278
Open
chikara1608 wants to merge 1 commit into
Open
test(ci): DO NOT MERGE — control experiment for test_node (20) failure#278chikara1608 wants to merge 1 commit into
chikara1608 wants to merge 1 commit into
Conversation
Adds a single HTML comment to README.md and nothing else. The dependency tree is untouched (package.json and package-lock.json are identical to main), so this isolates whether the `test_node (20)` matrix leg fails on any PR opened today regardless of its diff. Hypothesis: test/node/node.js installs unpinned `jsdom@latest`, and jsdom 30.x dropped Node 20 (engines ^22.22.2 || ^24.15.0 || >=26.0.0), so the Node 20 leg cannot install it. If this PR also fails test_node (20), the failure on #277 is environmental, not caused by that diff. Do not merge. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
This PR exists only to test a hypothesis about CI. Close it once the checks have reported.
What's in it
One HTML comment appended to
README.md. Nothing else:package.jsonandpackage-lock.jsonare byte-identical tomain— the dependency tree is completely untouched.The hypothesis
#277 (postcss + shell-quote overrides) fails
test_node (20). The claim is that this failure is environmental and unrelated to that diff:test/node/node.jsinstalls unpinnedjsdom@latestat test runtime, out of band, ignoring the lockfile. jsdom then dropped Node 20:jsdom@30.0.0published 2026-07-27,30.0.1on 2026-07-29jsdom@30.0.1declaresengines.node: "^22.22.2 || ^24.15.0 || >=26.0.0"So on the Node 20 matrix leg the install fails with
EBADENGINEand the followingrequire('jsdom')throwsMODULE_NOT_FOUND. The other legs reportCANCELLEDpurely from matrix fail-fast, which makes the blast radius look wider than it is.Supporting timeline — the same check passed on PRs whose runs predate the jsdom 30 releases:
test_node (20)How to read the result
test_node (20)→ confirmed. The break is dated, not diff-related, and chore(deps): security bumps — postcss, shell-quote (AXE-3900/AXE-3901) #277 is clear to merge on that basis. Every PR opened againstmainfrom now on will fail the same way until the unpinnedjsdom@latestis addressed.Follow-up either way
The unpinned
jsdom@latestintest/node/node.jsshould be pinned, or Node 20 dropped from the matrix. Note the repo's owndevDependenciespin isjsdom@^27.0.0, which works fine on Node 20 — only the runtime@latestinstall is the problem. That needs its own ticket; it is deliberately not fixed here.🤖 Generated with Claude Code