Uh oh!
There was an error while loading. Please reload this page.
[release/8.0-preview3] [browser] partial reversal of PR #82826 - #83750
Conversation
ghost
commented
Mar 22, 2023
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBackport of #83637 to release/8.0-preview3 Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
maraf
commented
Mar 22, 2023
Failures are not related. |
dbdf86d to
de6fa2cComparemarek-safar
commented
Mar 22, 2023
@carlossanlop@mmitche please merge before releasing |
carlossanlop
commented
Mar 22, 2023
@marek-safar@pavelsavara has this been approved by Tactics? |
marek-safar
commented
Mar 22, 2023
@carlossanlop I was under impression we are still in P3 open build window |
mmitche
commented
Mar 22, 2023
@leecow Are we doing tactics approval of p3 changes at this point? |
leecow
commented
Mar 22, 2023
This will need to be approved by Tactics since we've passed code-complete for Preview 3. |
carlossanlop
commented
Mar 22, 2023
Approved by Tactics via email. |
Backport of #83637 to release/8.0-preview3
/cc @maraf@pavelsavara
Customer Impact
Revert of making legacy JS interop trimmable. Blazor depends on it and the feature wasn't working correctly without wasm-tools workload.
Testing
Manual
Risk
None
IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.