-
Notifications
You must be signed in to change notification settings - Fork 165
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
Heads up of Node.js security releases 22nd September 2022 #3032
Comments
I'll lock the CI down tomorrow (21 September 2022). |
Thanks @richardlau let me know if you want me to update the message in Jenkins when it is done and thanks a lot for opening the discussion |
CI has now been locked down. |
Some fixes of the security releases have been recently updated and the Node.js security team still needs an extra day of work to ensure the binaries are ready to release. This means the CI will need to stay under embargo for one extra day. |
@richardlau the releases have been done, we can remove embargo. Thanks a lot! |
While the CI is locked down I'm going to try to swap over some servers that we need to migrate #3036. Shouldn't take too long 🤞. |
CI is now unlocked. FYI @nodejs/build I've swapped out the two jenkins-workspace machines that are data facilities earmarked for closure (#3028) onto freshly created machines. This includes moving the binary temp git repository that was on jenkins-workspace-4 (test-packetnet-ubuntu1804-x64-1) to the new jenkins-workspace-7 (test-equinix-ubuntu2204-x64-1). |
As per the Node.js security release process this is the FYI that there is going to be a security release on 22nd September 2022.
The text was updated successfully, but these errors were encountered: