-
Notifications
You must be signed in to change notification settings - Fork 10
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
Run cargo update
#1110
Run cargo update
#1110
Conversation
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
d035c1b
to
768ab90
Compare
c3c7281
to
f26100c
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.
I'd advise caution pairing a cargo update
with the larger hyper update. This is a lot of change to take on at once and it can lead to confounding bugs. I don't think lading will run any issues I'm aware of, but there have been some painful ones lurking here in the past.
Signed-off-by: Brian L. Troutwine <[email protected]>
768ab90
to
32aa9ca
Compare
f26100c
to
62509a4
Compare
I don't know to what degree I'll actually be able to upgrade hyper. I don't know the crate and its ecosystem well enough to understand the migration documentation and this is a change I don't have a lot of time to devote to. But, I've closed this PR out of an abundance of caution. |
What does this PR do?
Simple
cargo update