Skip to content
Closed
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 @@ -9,8 +9,8 @@
<PackageVersion Include="coverlet.collector" Version="8.0.1" />
<PackageVersion Include="GraphQL.Client" Version="6.1.0" />
<PackageVersion Include="GraphQL.Client.Serializer.SystemTextJson" Version="6.1.0" />
<PackageVersion Include="Microsoft.Extensions.Configuration" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Configuration.Json" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Configuration" Version="10.0.8" />
<PackageVersion Include="Microsoft.Extensions.Configuration.Json" Version="10.0.8" />
Comment on lines +12 to +13
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: The Microsoft.Extensions family of packages should typically be updated in unison. Having Configuration at 10.0.8 while Configuration.UserSecrets (line 14), DependencyInjection, Http, and Logging (lines 17-20) remain at 10.0.6 can lead to runtime version conflicts. These libraries are released as a suite and often share common dependencies; mixing versions is known to cause assembly resolution warnings or runtime errors. Try running the following prompt in your coding agent: > Update all Microsoft.Extensions.* package versions in Directory.Packages.props to 10.0.8.

<PackageVersion Include="Microsoft.Extensions.Configuration.UserSecrets" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.DependencyInjection" Version="10.0.6" />
<PackageVersion Include="Microsoft.Extensions.Http" Version="10.0.6" />
Expand Down
Loading