Update allowed binaries list#20689
Merged
marcpopMSFT merged 1 commit intoNov 4, 2025
Merged
Conversation
MichaelSimons
approved these changes
Oct 29, 2025
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Member
Author
|
Adding Adding |
Member
Author
|
I think we could merge this today - checking - @marcpopMSFT |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: dotnet/source-build#5391
All of these files are text files that are incorrectly flagged as binaries. The files are Unicode with a Unicode BOM. We already had exclusions for some other Unicode files. It is unclear why these files were suddenly flagged as binaries, but a likely suspect is the agent OS update to
ubuntu-22.04.This is not an issue in
mainorrelease/9.0.1xxas we useBinaryToolKitin those branches.