Repository navigation
fix(codec): make Browser runtime identity deterministic - #705
Merged
Merged
Conversation
SunSi12138
added a commit
that referenced
this pull request
Sep 18, 2026
Advance the main synchronization branch to the current dev tree after #705.
This was referenced Sep 18, 2026
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.
Follow-up to #704.
Release Gate #607 proved the Browser CoreCLR probe publishes and runs successfully under .NET 11 RC1, but also exposed that
Type.GetType("Mono.Runtime")is not a reliable Browser/WASM discriminator: the existing .NET 10 Mono Browser probe returned null and was misclassified as CoreCLR.Use the actual Browser probe build selection instead:
Monowithplatform-runtime-packprovenance;SHARPLINK_BROWSER_CORECLR/UseMonoRuntime=falsebuild recordsCoreCLRwithbuild-runtime-selectionprovenance.The runtime still records and validates observed TFM, RID, pointer size, framework/runtime version, SDK version, endianness, and compilation mode. This removes the unreliable reflection inference without weakening compatibility semantics.