-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Upgrade from Node.js v14.17.2 to v14.17.3 #104417
Conversation
Apparently Docker Hub is still not even ready with the image for last weeks upgrade. The reason for the test failures is that the latest 14.x image on Docker Hub is v14.17.1 😳 |
@watson merging now (minus Dockerfile changes) or waiting for a hub update both LGTM. Whichever's more convenient for you. |
14.17.2 is now on Docker hub, still waiting for 14.17.3. It should be very close though. Just waiting for nodejs/docker-node#1521 to make its way there |
Docker hub is now up to date - restarting build... |
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @watson |
Co-authored-by: Thomas Watson <[email protected]>
Co-authored-by: Thomas Watson <[email protected]>
I actually just wanted to get
.ci/Dockerfile
up-to-date with the Node.js upgrade from last week (#104148), however, yesterday a new patch for Node.js 14 was released which fixes an issue with the Windows installer. So in the interest of Kibana developers running Windows, I thought I'd better upgrade to that version.Other than the fix for the Windows installer, nothing has changed compared to the previous version.
Node.js 14.17.3 changelog: https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V14.md#14.17.3
Source for SHA256 hashes: https://nodejs.org/dist/v14.17.3/SHASUMS256.txt.asc