Flow CodeAnalysis analyzers version automatically - #55680
Open
marcpopMSFT wants to merge 1 commit into
Open
Conversation
Move Microsoft.CodeAnalysis.Analyzers into Maestro dependency metadata so dotnet/dotnet codeflow keeps it aligned with the other Roslyn components. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: a894e8d2-9b64-4080-9e62-0808907e8e11
|
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. |
Member
Author
|
@tannergooding moved this to auto update with codeflow per your comment here: #55654 (comment) |
Contributor
There was a problem hiding this comment.
Pull request overview
Moves the Microsoft.CodeAnalysis.Analyzers version pin from a manually maintained property in eng/Versions.props into Maestro dependency-flow metadata so it can be updated automatically alongside other Roslyn components flowing from dotnet/dotnet.
Changes:
- Remove the manual
MicrosoftCodeAnalysisAnalyzersVersionpin fromeng/Versions.props. - Add
Microsoft.CodeAnalysis.Analyzersas a flowed dependency ineng/Version.Details.xml. - Consume the flowed version via generated
eng/Version.Details.props(including a compatibility aliasMicrosoftCodeAnalysisAnalyzersVersion).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/Versions.props | Drops the manual analyzer version pin so the flowed value isn’t overridden. |
| eng/Version.Details.xml | Adds Microsoft.CodeAnalysis.Analyzers to Maestro-managed dependency metadata for codeflow updates. |
| eng/Version.Details.props | Introduces the generated package version and preserves the existing consumer-facing alias property. |
tannergooding
approved these changes
Aug 7, 2026
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.
The centrally pinned
Microsoft.CodeAnalysis.Analyzersversion can fall behind the Roslyn packages supplied by codeflow, causing package downgrade restore failures such as the one fixed in #55654.Move the analyzer version into Maestro dependency metadata so the existing
dotnet/dotnetcodeflow updates it alongside the other Roslyn components. The initial flowed version is5.11.0-1.26406.108, matching the current Roslyn dependency set, while the existingMicrosoftCodeAnalysisAnalyzersVersionconsumer property remains available through the generated compatibility alias.