ci: pin Node.js 24.x to 24.5.0 to fix CI failures#19813
Merged
alexander-akait merged 1 commit intowebpack:mainfrom Aug 17, 2025
Merged
ci: pin Node.js 24.x to 24.5.0 to fix CI failures#19813alexander-akait merged 1 commit intowebpack:mainfrom
alexander-akait merged 1 commit intowebpack:mainfrom
Conversation
Member
Author
|
@alexander-akait |
CodSpeed Performance ReportMerging #19813 will degrade performances by 70.68%Comparing Summary
Benchmarks breakdown
|
alexander-akait
approved these changes
Aug 17, 2025
Merged
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.
PR Description:
This PR pins Node.js 24.6 (=24.x) to version 24.5.0 in the CI workflow as a temporary workaround for a Node.js regression that causes CI failures.
Related to Node.js issue: nodejs/node#59480
What kind of change does this PR introduce?
CI/build configuration fix
Did you add tests for your changes?
N/A
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
None