Repository navigation
Validate IPv6 shortlist against family feed - #24
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.
Summary
ipv4_only.txtandipv6_only.txtfiles to exist, while allowing them to be empty if no candidates are available.top_ipv6.txtentry is absent fromipv6_only.txt. The collector builds the ranked IPv6 shortlist from the same IPv6-capable candidate pool, so this catches mismatched or truncated publication.Scope
Validator-only change; no source list, ranking policy, proxy output, or Cloudflare/WARP rule changes. CI validates the change before merge.