-
Notifications
You must be signed in to change notification settings - Fork 644
Bump to tokio 1.0
and hyper 0.14
#3117
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
Conversation
Update backend dependencies Pin `conduit-hyper` to the current version and do a `cargo update`. The version is pinned to avoid pulling in `tokio 1.0` until some remaining items in #3117 are resolved. r? `@Turbo87`
☔ The latest upstream changes (presumably #3149) made this pull request unmergeable. Please resolve the merge conflicts. |
☔ The latest upstream changes (presumably #3156) made this pull request unmergeable. Please resolve the merge conflicts. |
2d42412
to
ba88d9c
Compare
@jtgeibel I've updated |
tokio 1.0
and hyper 0.14
tokio 1.0
and hyper 0.14
Awesome, that was the last thing I was waiting for! r? @Turbo87 |
@bors r+ |
📌 Commit da3250f has been approved by |
☀️ Test successful - checks-actions |
To avoid pulling in 2 versions of
tokio
at once:hyper-tls 0.5
reqwest 0.11
oauth2
release depending onreqwest 0.11
- Bump totokio 1.0
andreqwest 0.11
ramosbugs/oauth2-rs#118sentry
release depending onreqwest 0.11
- Upgrade totokio 1.0
andreqwest 0.11
getsentry/sentry-rust#304r? @ghost