[NEXT-SECURITY-RELEASE] Heads up on upcoming Node.js security release 2024/07/02

[RafaelGSS]

As per security release workflow, creating issue to give the build team a heads up.

[richardlau]

I can handle locking/unlocking the CI. @RafaelGSS from when do you want the CI locked down?

In today's Build WG meeting we discussed perhaps extending the CI lockdown after the security release is done to handle some server migrations.

[RafaelGSS]

Once v22.4.0 is out, feel free to lock it down. I have the proposals ready to test, but I'm waiting v22.4.0 release to prepare v22 patch.

[richardlau]

CI has been locked down.
Announcement: https://github.com/nodejs/collaborators/discussions/199

[richardlau]

https://github.com/nodejs/collaborators/discussions/199#discussioncomment-10001115

Server migrations have been completed. CI restrictions have been lifted.

We have run test builds through the system, which appear to be working. If you spot any oddities, please open an issue in the Build repository.

Thank you for your patience.

To recap, we have migrated:

• github-bot to a new Debian 12 server.
• Equinix hosted jenkins-workspace machines to new MNX hosted ones. (Thanks @ryanaslett)
  • Including migration of the temporary binary git repository (70 Gb) used by the node-test-commit-arm-fanned and node-test-commit-windows-fanned jobs.