Repository navigation
chore: update Xray-core to v26.11.9 and refresh dependencies - #173
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
Synchronize the module pin, native build default, and English/Chinese build documentation. Refresh compatible transitive dependencies, including gVisor, uTLS, NAT discovery, root certificates, and Go tooling.
Use the REALITY/uTLS combination selected by the Core release and retain its compatible QUIC fork pin.
Evidence
After: both resolve the published v26.11.9 commit.
go test ./... -count=1, race tests,go vet ./..., module verification, tidy consistency, whitespace checks, and all 8 Python build tests on macOS.build/main.py apple go: 8 targets and 5 XCFramework slices; checked architectures, platforms, CGoInvoke/CGoFree exports, headers, and module maps.build/main.py android: AAR built for all 4 ABIs. Both native builders restored module files byte for byte.Native artifacts were inspected without app integration or live VPN acceptance. Linux/Windows runtime and their shared-library builds remain for CI/platform testing.
Merge Danger
Door: two-way
Revert the dependency commit to restore the previous versions.
Blast Radius: dependencies
Core runtime behavior can change across platforms; the wrapper API remains version 3.