[GH-ISSUE #639] Minimum Rust Version policy? #258

New issue

Open

opened 2026-03-07 23:04:15 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 23:04:15 +03:00

Owner

Originally created by @seanmonstar on GitHub (Dec 17, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/639

Does trust-dns have a minimum rust version policy? Such as keeping the same minimum Rust in patch versions, or something? I see a commented out minimum Rust in the CI, but I'm not sure what is the current minimum version.

For reference, I'm looking into changing the DNS resolver in reqwest, and noticed it doesn't seem to compile on Rust v1.29. Is that something you'd like to support? Or should I consider upgrading reqwest in its next breaking change?

Originally created by @seanmonstar on GitHub (Dec 17, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/639 Does trust-dns have a minimum rust version policy? Such as keeping the same minimum Rust in patch versions, or something? I see [a commented out minimum Rust in the CI](https://github.com/bluejekyll/trust-dns/blob/master/.travis.yml#L88-L89), but I'm not sure what is the current minimum version. For reference, I'm looking into [changing the DNS resolver in reqwest](https://github.com/seanmonstar/reqwest/pull/401), and noticed it doesn't seem to compile on Rust v1.29. Is that something you'd like to support? Or should I consider upgrading reqwest in its next breaking change?

kerem added the

question

label

2026-03-07 23:04:15 +03:00

kerem commented

2026-03-07 23:04:27 +03:00

Author

Owner

@bluejekyll commented on GitHub (Dec 18, 2018):

I have a vague desire to, but it’s not something I’ve been focused on. I think we could support 1.29 pretty easily at this point. If it helps in your adopting it, I’d be happy to keep a 1.29 build checked in CI.

After Futures stabilize in std, I guess we’ll need some way to detect 1.3x, as I’d want to support that API.

@bluejekyll commented on GitHub (Dec 18, 2018): I have a vague desire to, but it’s not something I’ve been focused on. I think we could support 1.29 pretty easily at this point. If it helps in your adopting it, I’d be happy to keep a 1.29 build checked in CI. After Futures stabilize in std, I guess we’ll need some way to detect 1.3x, as I’d want to support that API.

kerem commented

2026-03-07 23:04:32 +03:00

Author

Owner

@bluejekyll commented on GitHub (Dec 18, 2018):

I will say, the last time I spoke to @briansmith about this (trust-dns uses ring and rustls) he didn’t have an intention of supporting previous versions. That might be part of the reason why that CI validation was disabled.

@bluejekyll commented on GitHub (Dec 18, 2018): I will say, the last time I spoke to @briansmith about this (trust-dns uses ring and rustls) he didn’t have an intention of supporting previous versions. That might be part of the reason why that CI validation was disabled.

kerem referenced this issue

2026-03-15 22:25:55 +03:00

[GH-ISSUE #258] Replace chrono dependency with libstd dependency in -client #422