feat(edge): release routed endpoints and published TCP options - #32
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
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\n\n- add routed stream endpoints for every supported protocol\n- add published TCP options\n- harden asynchronous runtime, plugin discovery, packaging, caches, and Windows/MSVC portability\n\nThis branch replays the feature work onto the current main tree without the duplicated merge ancestry of the original WIP branch; its final tree is identical to that WIP tree.\n\n## Validation\n\n- Python build-script tests, CMake quality configuration, build, and CTest pass locally\n- the original identical feature tree passed the complete Linux, macOS, and Windows Conan matrix\n- secret and whitespace scans pass