Fix Microsoft.CodeAnalysis.Analyzers version mismatch - #55654
Conversation
Raise the central analyzer package version to the minimum required by the Roslyn packages currently flowing into main, preventing NU1109 restore failures in public CI. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 284ced01-d024-4c0b-b11a-16d2afbaee0b
|
Azure Pipelines: Successfully started running 1 pipeline(s). 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
There was a problem hiding this comment.
Pull request overview
Updates the centrally pinned Microsoft.CodeAnalysis.Analyzers package version to resolve restore failures (NU1109/NU1109-like “version outside dependency constraint”) caused by Roslyn package dependency minimums exceeding the current pin.
Changes:
- Bump
MicrosoftCodeAnalysisAnalyzersVersionineng/Versions.propsfrom5.10.0-1.26363.117to5.10.0-1.26365.3(consumed viaDirectory.Packages.props).
|
@tannergooding #55538 added this loose version for an analyzer but we end up getting a build break because of a mismatch: Should that version be pinned like that or should it get added to version.details.xml and moved into version.details.props and get auto-updated with codeflow? |
|
Should probably be auto-updated with codeflow, I just forgot that there was a secondary bit to do on that part. |
|
Failed from a hanging dotnet watch test 🔍 Force merging. |
Public main CI builds 1543163 and 1543195 fail restore with NU1109 because the newly added central
Microsoft.CodeAnalysis.Analyzerspin is lower than the minimum required by the Roslyn packages currently flowing into main.Update the central version from
5.10.0-1.26363.117to the minimum compatible5.10.0-1.26365.3. This preserves the intended analyzer dogfooding while avoiding unnecessary dependency churn.Validated by restoring the Razor SDK tool and Template Engine unit test projects that failed in CI.