-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/8.0-preview3] [browser] partial reversal of PR #82826 #83750
[release/8.0-preview3] [browser] partial reversal of PR #82826 #83750
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBackport of #83637 to release/8.0-preview3 /cc @maraf @pavelsavara 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.
|
Failures are not related. |
dbdf86d
to
de6fa2c
Compare
@carlossanlop @mmitche please merge before releasing |
@marek-safar @pavelsavara has this been approved by Tactics? |
@carlossanlop I was under impression we are still in P3 open build window |
@leecow Are we doing tactics approval of p3 changes at this point? |
This will need to be approved by Tactics since we've passed code-complete for Preview 3. |
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.