Repository navigation
network: DNS follows the policy, and offline asks nothing - #80
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follows spin-stack/spin#783; merge it after that one is released, since until then these pages promise what a running installation does not do.
"DNS always works" stops being true: a workspace's resolver now takes upstream only what its policy names,
offlineasks nothing, and a rule of narrow prefixes resolves no name.concepts/networksays so, andsecurity/indexkeeps the promise beside "reaches nothing".The generated reference (
file.md, the status page) is left to the nextsourcesbump.task buildcould not run here: this machine's Node is 22.22.1 and the site asks for >=22.23.4, so CI is the first build of this.🤖 Generated with Claude Code