Skip to content

Drop the hickory DNS feature - #8

Merged
JuliDi merged 1 commit into
mainfrom
julian/drop-hickory
Aug 7, 2026
Merged

Drop the hickory DNS feature#8
JuliDi merged 1 commit into
mainfrom
julian/drop-hickory

Conversation

@JuliDi

@JuliDi JuliDi commented Aug 6, 2026

Copy link
Copy Markdown
Member

Since hyper-hickory seems abandoned and depends on vulnerable versions of hickory, I decided to drop the hickory feature entirely.

We only make one DNS request to cloudflare.com and from then on it is cached anyway. So there is no big benefit of having hickory.

Plus: we get rid of a lot of transitive dependencies.

@JuliDi JuliDi self-assigned this Aug 6, 2026
@JuliDi
JuliDi force-pushed the julian/drop-hickory branch from dc8f3a2 to d0f3fb2 Compare August 7, 2026 07:41
Base automatically changed from julian/ci to main August 7, 2026 08:01
hyper-hickory replaced the default resolver with an async one, which this
crate does not benefit from: it posts to a single hostname over a pooled
connection, so DNS lookups are rare.

It doubled the dependency tree, from 74 to 150 crates, and pulled in
RUSTSEC-2026-0119 via hickory-proto 0.25, for which no fixed release is
reachable through hyper-hickory 0.8.

Also fix a stale cargo-make reference in Cargo.toml.
@JuliDi
JuliDi force-pushed the julian/drop-hickory branch from d0f3fb2 to c082d61 Compare August 7, 2026 08:03
@JuliDi
JuliDi requested review from joelsa and removed request for joelsa August 7, 2026 08:04
@JuliDi
JuliDi merged commit bb24d78 into main Aug 7, 2026
4 checks passed
@joelsa
joelsa deleted the julian/drop-hickory branch August 10, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant