Make HelixPublishWithArcade Compliant With The TargetOS Lowercasing Policy #85357
Conversation
This file contains 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
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsFixes #81141. In PR #80164, the build scripts were updated to always require and/or convert the MSBuild
|
trylek
approved these changes
Apr 25, 2023
ViktorHofer
approved these changes
Apr 25, 2023
jkoritzinsky
approved these changes
Apr 25, 2023
This was referenced Apr 26, 2023
akoeplinger
approved these changes
Apr 26, 2023
|
Failures are known issues. |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #81141. In PR #80164, the build scripts were updated to always require and/or convert the MSBuild
TargetOSproperty to lowercase. However, the helixpublishwitharcade.proj file was not included in these efforts, which led to some confusing behavior and misplaced files, as described in issue #81141. This PR addresses and fixes that.