Merged
Conversation
github-actions bot
added a commit
that referenced
this pull request
Mar 10, 2026
SHA: 79aacc4 Reason: push, by christhompson Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.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
1 participant
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.
This removes some of the remaining hand-wavey bits for the Fetching integration, particularly around how we get at the remote IP address, and removing the final unnecessary step around "public" IP address spaces.
PR #59 will address the TODO for the permissions check.
Codifying the integration with HTTP-network-or-cache fetch will be handled in a separate PR. For now, Section 4.3 serves as a baseline.