GH-36025: [JS] Allow Node.js 18.14 or later in verify-release-candidate.sh
#36089
Conversation
This file contains 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
Signed-off-by: abetomo <abe@enzou.tokyo>
Signed-off-by: abetomo <abe@enzou.tokyo>
…candidate.sh` Signed-off-by: abetomo <abe@enzou.tokyo>
github-actions
bot
added
awaiting merge
|
Conbench analyzed the 6 benchmark runs on commit There were 3 benchmark results indicating a performance regression:
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
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
In Node.js 18.14 or later,
gulp bundle:webpacksucceeds.So we support running
verify-release-candidate.shwith Node.js 18.14 or later.What changes are included in this PR?
Node.js version check allows 16, 18.14 or later.
Install Node.js LTS with
nvm.Are these changes tested?
I have tested that
TEST_DEFAULT=0 TEST_JS=1 dev/release/verify-release-candidate.shsucceeds in several environments.nvmandverify-release-candidate.shsucceeded.verify-release-candidate.shsucceeded.nvmandverify-release-candidate.shsucceeded.verify-release-candidate.shsucceeded.verify-release-candidate.shsucceeded.Are there any user-facing changes?