-
Notifications
You must be signed in to change notification settings - Fork 677
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] - Linkcheck fix #3452
Conversation
Oh I think we need to change the lighthouse book for the linkcheck to run in CI.. but this worked for me locally |
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.
Happy to try this, although I don't see how the chrono
issue is implicated
The mdbook docker container uses chrono, was digging into it earlier. Sorry for the lack of description 😊 |
bors r+ |
## Issue Addressed I think we're running into this in our linkcheck, so I'm going to frist verify linkcheck fails on the current version, and then try downgrading it to see if it passes chronotope/chrono#755 Co-authored-by: realbigsean <sean@sigmaprime.io>
Build failed (retrying...): |
## Issue Addressed I think we're running into this in our linkcheck, so I'm going to frist verify linkcheck fails on the current version, and then try downgrading it to see if it passes chronotope/chrono#755 Co-authored-by: realbigsean <sean@sigmaprime.io>
## Issue Addressed I think we're running into this in our linkcheck, so I'm going to frist verify linkcheck fails on the current version, and then try downgrading it to see if it passes chronotope/chrono#755 Co-authored-by: realbigsean <sean@sigmaprime.io>
Issue Addressed
I think we're running into this in our linkcheck, so I'm going to frist verify linkcheck fails on the current version, and then try downgrading it to see if it passes chronotope/chrono#755