Bump Microsoft.Extensions.Logging from 10.0.12 to 10.0.13

[dependabot]

Updated Microsoft.Extensions.Logging from 10.0.12 to 10.0.13.

Release notes

Sourced from Microsoft.Extensions.Logging's releases.

No release notes found for this version range.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[fossabot]

Needs Review

I recommend reviewing this upgrade before merging because the external security/snyk CI check is failing, and we cannot analyze its logs to determine whether the failure is related to this upgrade. The patch upgrade of Microsoft.Extensions.Logging is actively used in the codebase via src/algorithm_exercises_csharp_base/Logger.cs, which relies on core APIs (ILogger, ILoggerFactory, LoggerFactory.Create, LoggerMessage.Define) that are stable and unlikely to be affected by a patch bump. However, a version mismatch now exists in the project file between Microsoft.Extensions.Logging (bumped) and its sibling package Microsoft.Extensions.Logging.Console (still on the previous version), which should be reviewed for compatibility. The upgrade itself carries 1 new feature and 2 bug fixes, with no security vulnerabilities flagged for this package. Once the Snyk CI failure is investigated and the sibling package version alignment is confirmed, this upgrade can likely be safely merged.

Tip: Comment @​fossabot fix to attempt automatic fixes.

Fix Suggestions

We identified 2 fixable issues in this upgrade.

• Bump Microsoft.Extensions.Logging.Console from 10.0.12 to 10.0.13 to align with the upgraded Microsoft.Extensions.Logging version and eliminate version skew
  Files: src/algorithm_exercises_csharp_base/algorithm_exercises_csharp_base.csproj
• Investigate the failing security/snyk CI check to determine whether it is related to this upgrade or a pre-existing issue

AI Assistant Prompt

Copy prompt for AI assistant

## Fix Dependency Version Skew in algorithm-exercises-csharp

### Context
PR #448 upgraded `Microsoft.Extensions.Logging` from 10.0.12 to 10.0.13, but the sibling package `Microsoft.Extensions.Logging.Console` was left at 10.0.12. These packages are released together and should be kept in sync.

### Fix
In `src/algorithm_exercises_csharp_base/algorithm_exercises_csharp_base.csproj`, update the `Microsoft.Extensions.Logging.Console` package reference from version `10.0.12` to `10.0.13`.

Look for a line like:
```xml
<PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.12" />
```
Change it to:
```xml
<PackageReference Include="Microsoft.Extensions.Logging.Console" Version="10.0.13" />
```

After making the change, run `dotnet restore` and `dotnet build` to verify everything compiles correctly.

### Note
There is also a failing `security/snyk` CI check that needs manual investigation at the Snyk dashboard. This cannot be fixed via code changes — a human needs to review the Snyk report to determine if the failure is related to this upgrade or pre-existing.

What we checked

• Microsoft.Extensions.Logging is declared at the upgraded version 10.0.13 on this line. Its sibling package Microsoft.Extensions.Logging.Console on line 34 remains pinned at the prior version 10.0.12, creating a potential version skew between two packages that are typically released and consumed together. ^[1]
• Microsoft.Extensions.Logging is actively imported and used throughout this file. Core APIs consumed include ILogger (line 14), ILoggerFactory (line 15), LoggerFactory.Create (line 28), LogLevel (lines 23–25, 32), and LoggerMessage.Define (lines 48, 59, 70, 81). These are stable, fundamental abstractions unlikely to be affected by a patch-level change. ^[2]
• The security/snyk (sir-gon) external CI check is failing. Since this is an unsupported CI provider, its logs cannot be analyzed to determine whether the failure is related to this upgrade. Per review policy, any failing unsupported CI check requires manual review before merging. ^[3]

Dependency Usage

No usage of the analyzed dependencies was found in this repository.

• Microsoft.Extensions.Logging is declared at the upgraded version 10.0.13 on this line. Its sibling package Microsoft.Extensions.Logging.Console on line 34 remains pinned at the prior version 10.0.12, creating a potential version skew between two packages that are typically released and consumed together.
  

  algorithm-exercises-csharp/src/algorithm_exercises_csharp_base/algorithm_exercises_csharp_base.csproj

  Line 33 in 417b7e0

  <PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.13" />

• Microsoft.Extensions.Logging is actively imported and used throughout this file. Core APIs consumed include ILogger (line 14), ILoggerFactory (line 15), LoggerFactory.Create (line 28), LogLevel (lines 23–25, 32), and LoggerMessage.Define (lines 48, 59, 70, 81). These are stable, fundamental abstractions unlikely to be affected by a patch-level change.
  

  algorithm-exercises-csharp/src/algorithm_exercises_csharp_base/Logger.cs

  Line 3 in 417b7e0

  using Microsoft.Extensions.Logging;

Changes

Microsoft.Extensions.Logging was updated with two bug fixes that ensure configured NuGet sources and package source mappings are properly honored during template updates and workload integrity checks, alongside a new feature enabling package source mapping support for dotnet new install.

• Merged PR 65305: Honor configured NuGet sources during template update (eb00bec) (v10.0.13, changelog)
• Merged PR 65284: Honor package source mapping during workload integrity checks (32cd69c) (v10.0.13, changelog)
• Merged PR 65248: Enable package source mapping for dotnet new install (2293cdf) (v10.0.13, changelog)

View 9 more changes

• Merged PR 65256: [internal/release/10.0.4xx] Update dependencies from dnceng/internal/dotnet-dotnet (1644e94) (v10.0.13, changelog)
• [release/10.0.4xx] Source code updates from dotnet/arcade (#9408) (3073618) (v10.0.13, changelog)
• Merge commit '3073618cc1ab03586872e1cf3035afd377d66df6' (92b2ab7) (v10.0.13, changelog)
• Update dependencies from https://dev.azure.com/dnceng/internal/_git/dotnet-dotnet build 20260917.13 On relative base path root Microsoft.DotNet.Build.Manifest , Microsoft.DotNet.SignCheckTask From Version 10.0.0-beta.26467.107 -> To Version 10.0.0-beta.26467.113 Microsoft.NET.Sdk From Version 10.0.113-servicing.26467.107 -> To Version 10.0.113-servicing.26467.113 Microsoft.NETCore.App.Ref From Version 10.0.13 -> To Version 10.0.13 Microsoft.NETCore.Platforms From Version 10.0.13-servicing.26467.... (v10.0.13, changelog)
• [sdk] Source update 2c6e307 → 002ac71 Diff: https://redirect.github.com/dotnet/sdk/compare/2c6e3073c14e6e893c9bf059eb7716398b939315..002ac71bfdf0d553405fa25beea757687d8fa986 (892fc59) (v10.0.13, changelog)
• [templating] Source update 1fee620 → 14df6bb Diff: https://redirect.github.com/dotnet/templating/compare/1fee62075384159296295547471acf9a1cf6b7b2..14df6bb28555258e23a685c9d19fc3b0c05e953c (0475eaf) (v10.0.13, changelog)
• Update dependencies from build 332194 [[ commit created by automation ]] (fa35f47) (v10.0.13, changelog)
• [release/10.0.4xx] Source code updates from dotnet/source-build-assets (#9591) (ba2dc01) (v10.0.13, changelog)
• Merged PR 65717: merge 4xx > 402 no branding (665579e) (v10.0.13, changelog)

References (3)

[1]: Microsoft.Extensions.Logging is declared at the upgraded version 10.0.13 on this line. Its sibling package Microsoft.Extensions.Logging.Console on line 34 remains pinned at the prior version 10.0.12, creating a potential version skew between two packages that are typically released and consumed together.

algorithm-exercises-csharp/src/algorithm_exercises_csharp_base/algorithm_exercises_csharp_base.csproj

Line 33 in 417b7e0

<PackageReference Include="Microsoft.Extensions.Logging" Version="10.0.13" />

[2]: Microsoft.Extensions.Logging is actively imported and used throughout this file. Core APIs consumed include ILogger (line 14), ILoggerFactory (line 15), LoggerFactory.Create (line 28), LogLevel (lines 23–25, 32), and LoggerMessage.Define (lines 48, 59, 70, 81). These are stable, fundamental abstractions unlikely to be affected by a patch-level change.

algorithm-exercises-csharp/src/algorithm_exercises_csharp_base/Logger.cs

Line 3 in 417b7e0

using Microsoft.Extensions.Logging;

[3]: The security/snyk (sir-gon) external CI check is failing. Since this is an unsupported CI provider, its logs cannot be analyzed to determine whether the failure is related to this upgrade. Per review policy, any failing unsupported CI check requires manual review before merging. (source link)

---

fossabot analyzed this PR using dependency research and AI. View this analysis on the web

[fossabot]

[dependabot]

Superseded by #449.

[fossabot]

No Issues

No security issues were detected in the SAST scan. The code changes appear to follow secure coding practices.

---

fossabot analyzed this PR using SAST security analysis and AI (changed files only).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (0453b63) to head (417b7e0).

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #448   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           36        36           
  Lines          731       731           
  Branches        94        94           
=========================================
  Hits           731       731           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fossabot]