Skip to content

[release/9.0] [wasm] Include browser targets if RID is not wasi-wasm#108434

Merged
jeffschwMSFT merged 3 commits intorelease/9.0from
backport/pr-108283-to-release/9.0
Oct 11, 2024
Merged

[release/9.0] [wasm] Include browser targets if RID is not wasi-wasm#108434
jeffschwMSFT merged 3 commits intorelease/9.0from
backport/pr-108283-to-release/9.0

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Oct 1, 2024

Backport of #108283 to release/9.0

/cc @maraf

Customer Impact

  • Customer reported
  • Found internally

When publishing blazor app to azure containers, the VS wizard generates linux-x64 RID by default (wizard for publishing to folder correctly picks browser-wasm RID).

This PR makes the browser targets included any time when RID is not wasi-wasm, instead of relying on RID being browser-wasm.

Regression

  • Yes
  • No

The regression was introduced in #102806, where we started use Wasm SDK also for wasi targets and so we started to include browser targets only when RID is browser-wasm.

Testing

Manual test scenario.

Risk

Low. We have semantically reverted to previous behavior (include browser targets all the time with the exception for wasi).

@ghost ghost added the area-Build-mono label Oct 1, 2024
@maraf maraf added the arch-wasm WebAssembly architecture label Oct 1, 2024
@maraf maraf added this to the 9.0.0 milestone Oct 1, 2024
@dotnet-policy-service
Copy link
Contributor

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

@maraf maraf added the Servicing-consider Issue for next servicing release review label Oct 1, 2024
@jeffschwMSFT
Copy link
Member

removing servicing consider label until there is a template filled in

@jeffschwMSFT jeffschwMSFT removed the Servicing-consider Issue for next servicing release review label Oct 8, 2024
@maraf
Copy link
Member

maraf commented Oct 9, 2024

@jeffschwMSFT I have forget to remove template placeholder from first paragraph, otherwise the template is filled. Should I put more details in there?

@jeffschwMSFT
Copy link
Member

thanks @maraf , can you elaborate on how the fix addresses the issue? I will approve and we can send in email for approval

Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm. we will take for consideration in 9 GA

@jeffschwMSFT jeffschwMSFT added Servicing-consider Issue for next servicing release review Servicing-approved Approved for servicing release and removed Servicing-consider Issue for next servicing release review labels Oct 9, 2024
@jeffschwMSFT
Copy link
Member

please take a look at the pr failures.

@maraf
Copy link
Member

maraf commented Oct 11, 2024

All green now

@jeffschwMSFT jeffschwMSFT merged commit 3fcc122 into release/9.0 Oct 11, 2024
@maraf maraf deleted the backport/pr-108283-to-release/9.0 branch October 11, 2024 19:08
@github-actions github-actions bot locked and limited conversation to collaborators Nov 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

arch-wasm WebAssembly architecture area-Build-mono Servicing-approved Approved for servicing release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants