Skip to content

test(codec): add Browser CoreCLR compatibility evidence - #704

Merged
SunSi12138 merged 9 commits into
devfrom
test/browser-coreclr-codec-evidence-20260918
Sep 18, 2026
Merged

SunSi12138 merged 9 commits into
devfrom
test/browser-coreclr-codec-evidence-20260918

Conversation

@SunSi12138

Copy link
Copy Markdown
Owner

Add an experimental Browser/WASM CoreCLR codec evidence graph alongside the existing .NET 10 Mono Browser lane.

The CoreCLR lane:

  • pins .NET 11 RC1 SDK 11.0.100-rc.1.26425.128;
  • publishes the existing Browser probe as net11.0 with UseMonoRuntime=false;
  • requires the in-process identity browser-wasm-browser-coreclr-net11 / runtimeFamily=CoreCLR / wasm32;
  • verifies all six desktop producer corpora, the .NET 10 Browser Mono corpus, and CoreCLR self evidence in headless Chrome;
  • runs six reverse desktop consumers against the Browser CoreCLR corpus;
  • retains framework raw-layout evidence without materializing unsafe incompatible raw values.

The existing Mono Browser evidence remains unchanged. Every new CoreCLR job is continue-on-error: true, so the pre-GA .NET 11 runtime evidence cannot block the existing release contract.

auto-layout-release-scoped remains evidence-only for Browser <-> desktop edges and is extended to the explicit Mono Browser <-> CoreCLR Browser cross-runtime edge. Same-runtime Browser self-roundtrip and all non-auto-layout compatibility failures remain strict.

@SunSi12138
SunSi12138 merged commit 6ba3a8a into dev Sep 18, 2026
14 checks passed
@SunSi12138
SunSi12138 deleted the test/browser-coreclr-codec-evidence-20260918 branch September 18, 2026 11:19
SunSi12138 added a commit that referenced this pull request Sep 18, 2026
Advance the main synchronization branch to the current dev tree after #703 and #704.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant