[release/10.0.1xx] Source code updates from dotnet/deployment-tools#3121
Merged
dotnet-maestro[bot] merged 3 commits intorelease/10.0.1xxfrom Oct 29, 2025
Conversation
Diff: https://github.com/dotnet/deployment-tools/compare/c0c52874069a4dc0fe1e880014e6a5f316e9d3b8..84ccc0553245e90355f32ea8ddcf169d9bd8f640 From: dotnet/deployment-tools@c0c5287 To: dotnet/deployment-tools@84ccc05 [[ commit created by automation ]]
…8dda-296722556d59
…10.0.1xx-9b2fbfd0-184f-4d84-8dda-296722556d59
Contributor
Author
|
Note PRs from original repository included in this codeflow update:
💡 You may consult the FAQ for more information or tag @dotnet/product-construction for assistance. |
premun
approved these changes
Oct 29, 2025
dotnet-maestro
bot
deleted the
darc-release/10.0.1xx-9b2fbfd0-184f-4d84-8dda-296722556d59
branch
This was referenced Dec 9, 2025
Merged
Closed
Bump Microsoft.Extensions.Localization.Abstractions from 10.0.0 to 10.0.1
tiksn/TIKSN-Framework#2501
Closed
JanProvaznik
added a commit
that referenced
this pull request
Feb 12, 2026
Supersedes the previous EndsWith guard approach which didn't handle roslyn-versioned analyzers (RecursiveDir='dotnet/roslyn4.8/cs/' vs PackagePath='analyzers/dotnet/cs/' after version stripping). The fix: only read NuGetRecursiveDir (set by _GetTfmSpecificContentForPackage workaround) and stop falling back to the built-in RecursiveDir. Items that flow through other targets (sharedfx.targets, aspnetcore sfxproj) have already incorporated RecursiveDir into their PackagePath upstream, so appending it again is always wrong for those items. This handles all cases: - NETCore.App.Ref analyzers (RecursiveDir baked into TargetPath) - AspNetCore.App.Ref roslyn-versioned analyzers (RecursiveDir transformed) - Content items with NuGetRecursiveDir (workaround still works) - Old MSBuild (NuGetRecursiveDir was always the only source anyway) TODO: Remove NuGetRecursiveDir workaround entirely when minimum MSBuild includes the fix for #3121. See NuGet/Home#14413
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
1 participant
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.
Note
This is a codeflow update. It may contain both source code changes from the source repo as well as dependency updates. Learn more here.
This pull request brings the following source code changes
From https://github.com/dotnet/deployment-tools