Remove legacy nearby relay compatibility - #29
Merged
Conversation
jul-sh
marked this pull request as ready for review
July 25, 2026 19:12
jul-sh
force-pushed
the
agent/remove-legacy-nearby-relay
branch
from
August 12, 2026 17:27
aa8c6bc to
908c8d6
Compare
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.
Summary
PR #29 has been rebuilt on current
mainafter #32. The v8 implementation already removed the legacy nearby relay; this keeps that boundary permanent with focused regression coverage./relay/*and/v2/signal/*Worker routes#sand#kapproval fragments/room/*relay and exact#keyfragmentNo legacy compatibility code is restored or replayed from the old feature branch.
Validation
npm testinweb: 40 passinggit diff --check