[Dependencies] Updating Microsoft.CodeAnalysis.CSharp (Code Analysis) to 5.9.0 - #180
Conversation
Roslyn analyzer findings
|
ea3955a to
9082b02
Compare
… generator test projects Bumping Microsoft.CodeAnalysis.CSharp to 5.9.0 in the source generator projects surfaced a CS0433/CS1705 assembly version conflict in Credfeto.Database.Source.Generation.Tests and Credfeto.Database.Migrations.Source.Generation.Tests: both directly ProjectReference their source generator, and an analyzer package still resolves Microsoft.CodeAnalysis.CSharp 5.6.0 as the primary reference. Apply the documented RemoveGeneratorNuGetCompileDependencies target and pin an explicit 5.9.0 PackageReference, matching the pattern already used in Credfeto.Database.Source.Generation.Benchmark.Tests.csproj.
|
Fixed in ca3ea46 - resolved the Microsoft.CodeAnalysis.CSharp 5.6.0/5.9.0 assembly version conflict (CS0433/CS1705) in the two source-generator test projects that broke |
…target The target was duplicated verbatim across three test .csproj files (two added by the 5.9.0 version-conflict fix, one pre-existing in Benchmark.Tests). All three already import the shared UnitTests.props, so move the target there once and delete the per-project copies. Also corrects a stale version number left in the Benchmark.Tests override comment by the same version bump.
|
Simplify: applied cleanups - centralized the duplicated |
…sproj files Puts ProjectReference back before PackageReference, matching every other test project in the repo; the prior commit incidentally reordered these two while adding the Microsoft.CodeAnalysis.CSharp override.
|
Simplify: applied cleanups - restored conventional ItemGroup ordering (ProjectReference before PackageReference) in the two test csproj files, which had been incidentally reordered while adding the Microsoft.CodeAnalysis.CSharp override. Fixed in 9d31e67. |
|
Simplify clean - advancing to code review |
|
Code review clean - advancing to security review |
|
Security review clean, advancing to coverage check |
|
Non-code change - coverage ratchet skipped |
|
PR is ready: marked ready for review and auto-merge enabled. |
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Description
How Has This Been Tested
Types of changes
functionality to change)
Deployment Configuration Changes
Checklist
run:/script:body (workflow or composite action); pass it via step-levelenv:and reference$VAR(bash) orprocess.env.VAR(github-script) instead.