Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Directory.Packages.props
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,8 @@
<PackageVersion Include="coverlet.collector" Version="8.0.1" />
<PackageVersion Include="Codacy.Api" Version="3.0.22" />
<PackageVersion Include="Microsoft.Extensions.Configuration" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Configuration.Abstractions" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Configuration.Abstractions" Version="10.0.7" />
<PackageVersion Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.7" />
Comment on lines +20 to +21
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 MEDIUM RISK

Suggestion: Updating only a subset of the Microsoft.Extensions packages to 10.0.7 while leaving others (such as Microsoft.Extensions.Configuration at line 19 and Microsoft.Extensions.DependencyInjection at line 22) at 10.0.6 introduces version inconsistency. These packages are part of a synchronized ecosystem and should be kept on the same version to prevent 'diamond dependency' conflicts.

Try running the following prompt in your coding agent:

Update all Microsoft.Extensions.* package versions in Directory.Packages.props to 10.0.7 to maintain version parity across the framework.

<PackageVersion Include="Microsoft.Extensions.DependencyInjection" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Logging" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Options" Version="10.0.6" />
Expand Down
Loading