[release/10.0] [browser] Expect fingerprint on assemblies promoted from build #120548
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maraf
added
arch-wasm
|
Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara |
lewing
approved these changes
Oct 9, 2025
lewing
added
Servicing-approved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #120442 to release/10.0
/cc @maraf
In dotnet/sdk#50949 we changed the identity of StaticWebAsset to contain fingerprint (System.Private.Corelib.wasm -> System.Private.Corelib.FP.wasm). If we do relink, these assemblies from build are replaced by assemblies from relink. If we don't, we need to accommodate for the fingerprint when matching assets from build.
Customer Impact
Customers publishing the application without workload installed won't get expected set dlls copied to the publish output.
Fixes #120393
Regression
Testing
Manual verification and automated tests with SDK containing source of the issue.
Risk
Low. The publish is covered with automated tests.