-
Notifications
You must be signed in to change notification settings - Fork 168
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
Lock Down CI for 27th of march security release #1196
Comments
Happy to do this. |
I'd like to request that we start the lockdown in 6 hours. Does that seem reasonable to folks? explicitly 00:00 UTC |
Notice to collaborators --> nodejs/node#19642 |
CI has been locked down by @rvagg |
security release is done, can someone unlock CI? |
@nodejs/build ci is still locked... |
I've gone ahead and changed the permissions... I think I did it right |
Hey All,
We are going to need to lock down CI from tomorrow until the security release is out the door. Would someone from build be able to take point on doing this? More than happy to open an issue on the main repo to let collaborators know, but don't want to do so until someone has volunteered
The text was updated successfully, but these errors were encountered: