ci: fix rust-docs build #4415
Merged
ci: fix rust-docs build #4415
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumped the `time` crate in order to resolve a build error with recent rust nightlies on the `rust-docs` build. Also removed the `index.html` file generated for rust-docs from version control, since that file is built on the fly in CI post-merge, and so will always be out of date.
conorsch
added
the
A-CI/CD
conorsch
added
the
C-chore
|
See example failing build here: https://github.com/penumbra-zone/penumbra/actions/runs/9158128504/job/25175841362?pr=4413 the |
erwanor
approved these changes
May 20, 2024
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Bumped the
timecrate in order to resolve a build error with recent rust nightlies on therust-docsbuild. Also removed theindex.htmlfile generated for rust-docs from version control, since that file is built on the fly in CI post-merge, and so will always be out of date.Issue ticket number and link
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: