Skip to content

fix(deps): update rust crate hickory-resolver to 0.25 #48

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update rust crate hickory-resolver to 0.25 #48

wants to merge 1 commit into from

Conversation

@stackable-bot
Copy link
Contributor

@stackable-bot stackable-bot commented Aug 5, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
hickory-resolver (source) dependencies minor 0.24 -> 0.25

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

hickory-dns/hickory-dns (hickory-resolver)

v0.25.2: 0.25.2

Compare Source

What's Changed

v0.25.1: 0.25.1

Compare Source

This is a small patch release to address errors that prevented publication of version 0.25.0 of some crates.

What's Changed

Full Changelog: hickory-dns/hickory-dns@v0.25.0...v0.25.1

v0.25.0: 0.25.0

Compare Source

0.25.0 represents a large release for the Hickory DNS project. Over 14 months since 0.24.0, we've added two new maintainers, divergentdave and marcus0x62, and have addressed many limitations. A team from Ferrous Systems shored up our support for DNSSEC, and we addressed a number of findings from our first security audit.

Breaking changes

This is not an exhaustive list of changes, but here are some of the most impactful breaking changes in this release:

  • Configuration for the Hickory DNS server crate has been reworked substantially to be more robust and secure. Most of the code related to the server binary has been moved out of the hickory-server library and into the hickory-dns binary crate.
  • Support for TLS using native-tls or OpenSSL has been removed. We now only provide first-party support for rustls (0.23, for DNS over TLS, HTTP/2, QUIC and HTTP/3). We support ring or aws-lc-rs for cryptographic operations both for DNSSEC and TLS. The dns-over-rustls,dns-over-native-tls, dns-over-openssl, dns-over-https-rustls, dns-over-https, dns-over-quic and dns-over-h3 features have been removed in favor of a set of {tls,https,quic,h3}-{aws-lc-rs,ring} features across our library crates.
  • The synchronous API in the resolver and client crates, which previously provided a thin partial wrapper over the asynchronous API, has been removed. Downstream users will have to migrate to the asynchronous API.
  • Support for the async-std runtime has been removed following the deprecation of the async-std crate by upstream (see their README). The async-std-resolver crate will no longer be updated.
  • The DNSSEC API was reworked to extend coverage to the recursor, add support for NSEC3, and make the API more ergonomic and harder to misuse.
  • Moved the RuntimeProvider API into the proto crate and use it consistently across the project.
  • Name values are now rooted by default in many places, and more consistently maintain their fqdn status.
  • Error types are now exposed directly in the crate roots.
  • Top-level TLS configuration in the resolver crate has moved to the ResolverOpts type. Specific NameServerConfigs should implicitly set up the ALPN protocol appropriate for the DNS protocol.
  • The ResolverOptions fields authentic_data and shuffle_dns_servers were removed. The former field didn't do anything; and should be covered by new DNSSEC API. shuffle_dns_servers functionality has been subsumed into the server_ordering_strategy field.
  • The use of rustls-native-certs via the native-certs feature was replaced with rustls-platform-verifier.
  • The tokio-runtime feature was renamed to tokio.
  • The serde-config feature was renamed to serde.
  • Serializations (and what the new release can deserialize) has changed; data serialized by 0.24 may not deserialize correctly on 0.25, and vice versa.

Please don't hesitate to file an issue or ask on our Discord server if you have issues upgrading.

Detailed changes since alpha.5

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@stackable-bot
fix(deps): update rust crate hickory-resolver to 0.25
b978f4e 
| datasource | package          | from   | to     |
| ---------- | ---------------- | ------ | ------ |
| crate      | hickory-resolver | 0.24.4 | 0.25.2 |
@stackable-bot stackable-bot added the dependencies Pull requests that update a dependency file label Aug 5, 2025
@stackable-bot stackable-bot requested a review from a team August 5, 2025 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@stackable-bot