This repository was archived by the owner on Oct 24, 2026. It is now read-only.
Repository navigation
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Select patched Node22.23.4 in .nvmrc and CI, and bound existing application runtime declarations to the fixed Node22 branch. Expand workflow path filters to test runtime-policy changes.
Application dependency versions and dependency lockfiles are unchanged.
Evidence
Node22.23.4 security release explicitly fixes CVE-2026-111497. Hardhat2.22.6 added Node22 support.
Verification
Changed JSON/YAML parsed. CI installed Node 22.23.4 successfully but dependency installation failed: the existing locked @ensdomains/buffer 0.1.1 tarball returns HTTP404. Contract tests never started. No unrelated dependency upgrade or lockfile rewrite was made.
Remaining rollout and limits
The Node 18-to22 migration is selected in .nvmrc and root engines are bounded to the fixed Node 22 branch; CI uses .nvmrc. Resolve the existing missing tarball before considering compatibility validated. Update any external Node installations separately.
No exploit probes were run. A runtime selection fix is not production deployment verification. This remains a draft for review; nothing was merged or deployed manually.