-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Reduce latency when new node versions are released #160
Comments
The same thing is true when specifying "v12.x". If one wants the latest version one must specify it explicitly. I needed something later than the version 12.16.3 it was grabbing when given "v12.x", so I wrote "v12.18.0" for my node-version. This is not that great though, since I wish to always use the latest release. |
Hello everyone, just to clarify how it works:
Unfortunately, pre-cached versions are updated with small delay (usually, not longer than 1-1.5 weeks because images rollout takes much effort) so if you specify full version, action doesn't find it on image and downloads and installs it in runtime. If you just specify @bryanmacfarlane , may be some flag similar to |
Yes, @maxim-lobanov is correct. You can specify the exact version you need and we'll read through the cache and I'm happy to add the If you don't mind, I'm going to morph this issue into a tracking item for adding option to always get latest. OK? |
@bryanmacfarlane , That sounds good to me! |
I think we should enhance the actions/node-versions releases so they are updated everyday. That (1) provides the reliability we get from releases / CDN while at the same time (2) offering new versions with minimal latency. Reading through directly to node dist will completely eliminate the latency but at the same time, it will expose the fragility of failed downtimes when new releases are made from node - the very scenario here. |
This enlightenment was awesome! |
Hello everyone. The Related pull request: #165 For now I'm closing the issue. If you have any concerns feel free to ping us. |
to avoid issues downloading new versions see actions/setup-node#160 (comment) for more context
to avoid issues downloading new versions see actions/setup-node#160 (comment) for more context
This commit upgrades Node.js version to v20.x in CI/CD environment. Previously used Node 18.x is moving towards end-of-life, with a planned date of 2025-04-30. In contrast, Node 20.x has been offering long-term support (LTS) since 2023-10-24. This makes Node 20.x a stable and recommended version for production environments. This commit also configures `actions/setup-node` with the `check-latest` flag to always use the latest Node 20.x version, keeping CI/CD setup up-to-date with minimal maintenance. Details: - actions/setup-node#165 - actions/setup-node#160 Using Node 20.x in CI/CD environments provides better compatibility with Electron v29.0 which moves to Node 20.x. Details: - electron/electron#40343 This upgrade improves network connection handling in CI/CD pipelines (where issues occur due to GitHub runners not supporting IPv6). Details: - actions/runner#3138 - actions/runner-images#668 - actions/runner#3213 - actions/runner-images#9540 Node 20.x adopts the Happy Eyeballs algorithm for improved IPv6 connectivity. - nodejs/node#40702 - nodejs/node#41625 - nodejs/node#44731 This mitigates issues like `UND_ERR_CONNECT_TIMEOUT` and localhost DNS resolution in CI/CD environments: Details: - nodejs/node#40537 - actions/runner#3213 - actions/runner-images#9540 Node 20 introduces `setDefaultAutoSelectFamily`, a global function from Node 19.4.0, enabling better IPv4 support, especially in environments with limited or problematic IPv6 support. Details: - nodejs/node#45777 Node 20.x defaults to the new `autoSelectFamily`, improving network connection reliability in GitHub runners lacking full IPv6 support. Details: - nodejs/node#46790
This commit upgrades Node.js version to v20.x in CI/CD environment. Previously used Node 18.x is moving towards end-of-life, with a planned date of 2025-04-30. In contrast, Node 20.x has been offering long-term support (LTS) since 2023-10-24. This makes Node 20.x a stable and recommended version for production environments. This commit also configures `actions/setup-node` with the `check-latest` flag to always use the latest Node 20.x version, keeping CI/CD setup up-to-date with minimal maintenance. Details: - actions/setup-node#165 - actions/setup-node#160 Using Node 20.x in CI/CD environments provides better compatibility with Electron v29.0 which moves to Node 20.x. Details: - electron/electron#40343 This upgrade improves network connection handling in CI/CD pipelines (where issues occur due to GitHub runners not supporting IPv6). Details: - actions/runner#3138 - actions/runner-images#668 - actions/runner#3213 - actions/runner-images#9540 Node 20.x adopts the Happy Eyeballs algorithm for improved IPv6 connectivity. - nodejs/node#40702 - nodejs/node#41625 - nodejs/node#44731 This mitigates issues like `UND_ERR_CONNECT_TIMEOUT` and localhost DNS resolution in CI/CD environments: Details: - nodejs/node#40537 - actions/runner#3213 - actions/runner-images#9540 Node 20 introduces `setDefaultAutoSelectFamily`, a global function from Node 19.4.0, enabling better IPv4 support, especially in environments with limited or problematic IPv6 support. Details: - nodejs/node#45777 Node 20.x defaults to the new `autoSelectFamily`, improving network connection reliability in GitHub runners lacking full IPv6 support. Details: - nodejs/node#46790
Hi there:
Thanks for this library. Just found that the
node-version
option is not downloading the latest node release.v10.21.0 release notes:
https://nodejs.org/en/blog/vulnerability/june-2020-security-releases/
Our setup:
Logs:
Update:
seems related to this change: #147
Regards
Ken
The text was updated successfully, but these errors were encountered: