Skip to content

v0.5.3: TLS webpki-roots trust and CI adjustments#1

Merged
l1a merged 3 commits into
masterfrom
dev
Apr 24, 2026
Merged

v0.5.3: TLS webpki-roots trust and CI adjustments#1
l1a merged 3 commits into
masterfrom
dev

Conversation

@l1a

@l1a l1a commented Apr 24, 2026

Copy link
Copy Markdown
Owner

Changes

  • TLS Fixes: Added the webpki-roots feature to hickory-resolver. When using --tls or --https, hickory-resolver requires a root certificate trust store for rustls to validate server certificates. This prevents connections from being incorrectly dropped as connection refused.
  • CI Enhancements: Removed redundant CI execution on master pushes to prevent tests from firing twice when tagging releases.
  • Version Bump: Bumped project version to 0.5.3.

l1a added 3 commits April 24, 2026 09:36
- When using  or ,  requires a root certificate trust store for  to validate server certificates.
- Because  was omitted, the DNS-over-TLS client had zero trusted CAs, causing all TLS handshakes to instantly fail.
- These TLS failures were bubbling up as confusing  or  errors depending on the nameserver permutation.
- Added the  feature to ensure TLS connections to nameservers (like 1.1.1.1 and 8.8.8.8) succeed.
- Remove  from the  trigger in .
- When a tag (e.g. ) is pushed to , both the  workflow (triggered by the tag) and the  workflow (triggered by the push to ) were running simultaneously, causing duplicate and wasteful runner execution.
- Now, standard tests and linting will only automatically run on the  branch directly, or when Pull Requests are opened against .
@l1a l1a changed the title Fix: TLS webpki-roots trust and CI adjustments v0.5.3: TLS webpki-roots trust and CI adjustments Apr 24, 2026
@l1a

l1a commented Apr 24, 2026

Copy link
Copy Markdown
Owner Author

Cool beans!

@l1a l1a merged commit f963a41 into master Apr 24, 2026
8 checks passed
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