[build] Bump arcade for latest SxS manifest fixes #8280
Merged
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
Context: dotnet/arcade@b6e1c2f Updates the arcade version to bring in a fix for workload MSI generation when side by side manifest support is enabled. This should allow us to avoid an issue that would occur when trying to insert a new workload manifest with the same SDK band as the one already in VS.
Member
Author
jonathanpeppers
approved these changes
Aug 18, 2023
Member
jonathanpeppers
left a comment
jonathanpeppers
left a comment
There was a problem hiding this comment.
Going to merge this, so we can do a test / Visual Studio insertion.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Context: dotnet/arcade@b6e1c2f
Updates the arcade version to bring in a fix for workload MSI generation
when side by side manifest support is enabled. This should allow us to
avoid an issue that would occur when trying to insert a new workload
manifest with the same SDK band as the one already in VS.