You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we are prepping for a security release going out at some point in the next 48 hours we will need to lock down CI to test the embargoed changes and release. During the lockdown we kindly request that you avoid launching jobs unrelated to the release if you still have access. Jobs unrelated to the release will be shut down.
We hope to have the CI resources available to the general collaborators in a timely fashion. You can track the status of the build team in this issue. This issue will be kept up to date with the status, especially if we think CI will need to be locked down for more than 12 hours.
Thank you for your patience and understanding.
The text was updated successfully, but these errors were encountered:
Hey @nodejs/collaborators
As we are prepping for a security release going out at some point in the next 48 hours we will need to lock down CI to test the embargoed changes and release. During the lockdown we kindly request that you avoid launching jobs unrelated to the release if you still have access. Jobs unrelated to the release will be shut down.
We hope to have the CI resources available to the general collaborators in a timely fashion. You can track the status of the build team in this issue. This issue will be kept up to date with the status, especially if we think CI will need to be locked down for more than 12 hours.
Thank you for your patience and understanding.
The text was updated successfully, but these errors were encountered: