Skip to content

[browser][coreclr] Strip workload content #134074

Description

@maraf

We should strip content of workload to a minimum, which is the required large payload of the emscripten. The goal is to be able to version (and force update) together components that possibly may contain servicing patches.

  • Runtime pack, crossgen and build targets should like in the SDK the same way as on other platforms
  • Emscripten binaries and minimal targets (mostly containing location logic) should be part of the workload

We don't expect to change/bump emscripten in the servicing releases. Binary location logic thus should be very constant. Any build logic related to the emscripten invocation should be tightly coupled with the rest of the runtime pack and SDK pack by versioning it with the .NET SDK itself.

  • Clean-up targets in the emscripten workload
  • Remove runtime pack and SDK pack from the workload manifest
  • Move build logic from workload packs to the SDK pack. We need to maintain compatibility with down level targeting
  • Refactor Wasm.Build.Tests setup to not depend on runtime pack and sdk pack being part of workload manifest

Activity

  1. added this to the 12.0.0 milestone on Sep 16, 2026
  2. dotnet-policy-service commented on Sep 16, 2026

    @dotnet-policy-service
    Contributor

    Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
    See info in area-owners.md if you want to be subscribed.

  3. pavelsavara commented on Sep 16, 2026

    @pavelsavara
    Member

    LLVM ABI vs crossgen ABI vs runtime pack ABI of the .a files and things like ICU

  4. added
    NO-MERGEThe PR is not ready for merge yet (see discussion for detailed reasons)
    and removed
    NO-MERGEThe PR is not ready for merge yet (see discussion for detailed reasons)
    on Sep 17, 2026
  5. changed the title [-][browser][coreclr] Workload content[/-] [+][browser][coreclr] Strip workload content[/+] on Sep 21, 2026
  6. self-assigned this
    on Sep 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions