mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[PR #1852] [CLOSED] Fix all Tokio usage to version to 1.21. #2654
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#2654
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/hickory-dns/hickory-dns/pull/1852
Author: @darnuria
Created: 12/4/2022
Status: ❌ Closed
Base:
main← Head:tokio-one-version📝 Commits (1)
d9cc7e2Fix all Tokio usage to version to 1.21.📊 Changes
7 files changed (+11 additions, -11 deletions)
View changed files
📝
crates/client/Cargo.toml(+2 -2)📝
crates/proto/Cargo.toml(+2 -2)📝
crates/recursor/Cargo.toml(+2 -2)📝
crates/resolver/Cargo.toml(+1 -1)📝
crates/server/Cargo.toml(+1 -1)📝
tests/integration-tests/Cargo.toml(+2 -2)📝
util/Cargo.toml(+1 -1)📄 Description
I was wondering why trust-dns build where so big so I went doing some dependencies version inspection. Don't know what will be the impact but it's still interesting.
Did a really simple
rg -A 10 dependencies **/cargo.tomlto have a first quick summary.(will add cargo lock after my
cargo make all-featureends)🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.