Prepare 1.3.3 recursion hotfix release - #156
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepare the 1.3.3 hotfix with curated release notes and updated handbook version metadata. Fix three failures in direct recursive resolution:
.comnameservers undergtld-servers.net, avoidingdelegation for com. has no resolvable name servers. Glue remains limited to named servers within the referring parent's scope.Validation:
go test -race ./internal/dnsserver -count=1passes, including existing out-of-bailiwick glue rejection tests.cloudflare.com,ietf.org, andexample.netreturned DNSSEC-secure answers with a three-second resolution timeout. The network-dependent probe was run separately from the committed tests.git diff --checkpasses.Release preparation:
VERSION=1.3.3 go tool mage releaseGatepassed: generated-code checks, Mage/application tests, static analysis, standalone and two-node cluster binary smoke tests, GoReleaser validation, all eight platform archives, and multi-architecture Docker snapshot builds with native container smoke checks. The first gate attempt hit the existing QUIC shutdown timing test; it passed ten isolated repetitions and the gate rerun. Release-note extraction forv1.3.3succeeds. No release tag or publication has been created; after merging, dispatch the Release workflow frommainwith version1.3.3.