GH-46787: [CI][Integration] Use Node.js 20 #46790
Merged
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
|
|
Member
Author
|
+1 |
This was referenced Jun 13, 2025
alinaliBQ
pushed a commit
to Bit-Quill/arrow
that referenced
this pull request
Jun 17, 2025
### Rationale for this change Node.js 18 reached EOL on 2025-04-30: https://github.com/nodejs/release#release-schedule ### What changes are included in this PR? Use Node.js 20. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * GitHub Issue: apache#46787 Authored-by: Sutou Kouhei <[email protected]> Signed-off-by: Sutou Kouhei <[email protected]>
|
After merging your PR, Conbench analyzed the 0 benchmarking runs that have been run so far on merge-commit 9133598. None of the specified runs were found on the Conbench server. The full Conbench report has more details. |
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.
Rationale for this change
Node.js 18 reached EOL on 2025-04-30: https://github.com/nodejs/release#release-schedule
What changes are included in this PR?
Use Node.js 20.
Are these changes tested?
Yes.
Are there any user-facing changes?
No.