-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CI][Release][JS] Node.js 16 is old for verification #39020
Comments
kou
added a commit
to kou/arrow
that referenced
this issue
Dec 1, 2023
kou
added a commit
to kou/arrow
that referenced
this issue
Dec 1, 2023
kou
added a commit
to kou/arrow
that referenced
this issue
Dec 1, 2023
kou
added a commit
to kou/arrow
that referenced
this issue
Dec 1, 2023
kou
added a commit
to kou/arrow
that referenced
this issue
Dec 1, 2023
kou
added a commit
that referenced
this issue
Dec 1, 2023
### Rationale for this change Node.js 16 reached EOL. ### What changes are included in this PR? Use Node.js 18. It's the oldest maintained LTS. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: #39020 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
dgreiss
pushed a commit
to dgreiss/arrow
that referenced
this issue
Feb 19, 2024
…e#39021) ### Rationale for this change Node.js 16 reached EOL. ### What changes are included in this PR? Use Node.js 18. It's the oldest maintained LTS. ### Are these changes tested? Yes. ### Are there any user-facing changes? No. * Closes: apache#39020 Authored-by: Sutou Kouhei <kou@clear-code.com> Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the enhancement requested
Node.js 16 reached EOL: https://nodejs.org/en/about/previous-releases
Our release verification CI job is also started failing:
https://github.com/ursacomputing/crossbow/actions/runs/7005228039/job/19054548400#step:7:39
Component(s)
JavaScript, Release
The text was updated successfully, but these errors were encountered: