Bump node from 24.17.0 to 24.18.0#8233
Merged
Merged
Conversation
Contributor
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Contributor
jdolle
approved these changes
Jul 17, 2026
Contributor
|
🐋 This PR was built and pushed to the following Docker images: Targets: Platforms: Image Tags: |
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
2 participants
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 bumps Node from 24.17.0 to 24.18.0 to fix the
changeset-versionCI job hanging until it hits its step timeout.Node 24.17.0 shipped a security fix (CVE-2026-48931, "http: fix response queue poisoning in http.Agent") that regressed keep-alive socket reuse: it attaches a public
datalistener to idle pooled sockets, which node-fetch@2 misreads as a broken stream.@changesets/get-github-info@0.8.0(used by@changesets/changelog-githubto enrich each changeset via the GitHub GraphQL API) calls node-fetch@2 with no timeout, so a corrupted reused socket stallspnpm changeset versionsilently until the job is killed. This is not fixable by updating changesets (we're already on the latest versions)...it's an upstream Node bug, fixed in Node 24.18.0 via nodejs/node#64004. 24.18.0 keeps the CVE-2026-48931 security fix while restoring correct keep-alive behavior.Refs: nodejs/node#63989 (nodejs/node#63989), nodejs/node#64004 (nodejs/node#64004), changesets#2115 (changesets/changesets#2115), CVE-2026-48931.