You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
### Rationale for this change
Node.js 16 is soon to be EOL, so we will use Node.js 18 with CI.
### What changes are included in this PR?
Use Node.js 18 at `name: NodeJS` in GitHub Actions.
### Are these changes tested?
* I ran `archery docker run debian-js` locally and succeeded
* GitHub Actions `name: NodeJS` succeeds
* https://github.com/abetomo/arrow/actions/runs/5289906862/jobs/9589326158
* `docker` and `windows` succeeded
* In the GitHub Actions for my repository, `macos` timed out. Has it happened before?
### Are there any user-facing changes?
* Closes: #36055
Authored-by: abetomo <abe@enzou.tokyo>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Describe the enhancement requested
https://github.com/nodejs/release#release-schedule says that Node.js 16 will reach EOL on 2023-09-11.
Our JavaScript related CI jobs use Node.js 16:
Should we use Node.js 18 instead of 16?
@domoritz What do you think about this?
Component(s)
JavaScript
The text was updated successfully, but these errors were encountered: