Skip to content
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

Update node version #208

Closed
giordano opened this issue Jan 22, 2024 · 2 comments · Fixed by #209
Closed

Update node version #208

giordano opened this issue Jan 22, 2024 · 2 comments · Fixed by #209

Comments

@giordano
Copy link
Member

Node 16 is deprecated

using: 'node16'

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

@DilumAluthge
Copy link
Member

DilumAluthge commented Jan 28, 2024

Quoting from my comment here:

Node20 requires glibc 2.28.

CentOS 7 ships with glibc 2.17. Therefore, once we upgrade julia-actions/setup-julia to Node20, self-hosted CentOS 7 runners won't be able to use new versions of the setup-julia action.

CentOS 7 will become end-of-life on June 30, 2024. Therefore, I think that we should wait until June 30 to upgrade setup-julia to Node20.


CentOS 8 ships with glibc 2.28. Therefore, self-hosted CentOS 8 runners will be able to run Node20.

@WardBrian
Copy link

GitHub is suggesting that node 16 support would be dropped before June:

Our plan is to transition all actions to run on Node 20 by Spring 2024

It would be great if v2 tag was published with node 20 support. People using runners that cannot run node 20 can stay on the previous major version, as they will currently also have to do with actions such as cache, upload-artifact, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants