-
Notifications
You must be signed in to change notification settings - Fork 10.4k
[release/8.0] [Blazor] Fix Microsoft.AspNetCore.Components.WebView.props
not getting packed correctly
#52971
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
Conversation
Hi @github-actions[bot]. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge. To learn more about how to prepare a servicing PR click here. |
Hi @github-actions[bot]. This PR was just approved to be included in the upcoming servicing release. Somebody from the @dotnet/aspnet-build team will get it merged when the branches are open. Until then, please make sure all the CI checks pass and the PR is reviewed. |
Backport of #52638 to release/8.0
/cc @MackinnonBuck
Fix
Microsoft.AspNetCore.Components.WebView.props
not getting packed correctlyFixes an issue where
Microsoft.AspNetCore.Components.WebView.props
was not getting packed correctly. This was causing build failures for any project referencingMicrosoft.AspNetCore.Components.WebView
.Description
Fixes #52637
Customer Impact
If customers were to reference a new version of this package without this fix, their app would fail to build. Our temporary workaround is to avoid shipping new versions of
Microsoft.AspNetCore.Components.WebView
until this issue gets fixed.Regression?
Regressed from package version 8.0.0.
Risk
The fix is straightforward, and we've verified that the packages produced in CI contain the correct assets. A MAUI dependency update was failing due to this bug, and the fix has shown to address it.
Verification
Packaging changes reviewed?