-
Notifications
You must be signed in to change notification settings - Fork 801
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
[Merged by Bors] - Update holesky config for relaunch #4760
Conversation
a1cfde2
to
69a8a7a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect! I've checked the changes to config.yaml
, boot ENRs and checked that it verifies the state we've put up on AWS S3!
bors r+ I just missed a batch but I'll throw this into bors in case there's a failure and it gets picked up. |
Build failed: |
bors r+ |
Pull request successfully merged into unstable. Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page.
|
Issue Addressed
#4759
Note: Sigma Prime ENR hasn't been updated, tracking it in #4759