[kkdev92]

Keeps Microsoft.Extensions.Http and Microsoft.Extensions.Options on the 10.0 line by ignoring major updates for the pair in dependabot.yml.

Why

The DependencyInjection package references both packages directly, so the versions in Directory.Packages.props become the dependency lower bounds in its nuspec (10.0.14 for both in the 0.10.1-alpha package). #121 proposes 11.0.0 for the pair. Merging it would raise every consumer to the 11.0 Microsoft.Extensions packages, apps still on .NET 10 included, while the packages target net10.0 only.

What changed

• .github/dependabot.yml: an ignore list on the NuGet entry with version-update:semver-major for Microsoft.Extensions.Http and Microsoft.Extensions.Options, and a comment that says when to remove it (net11.0 joining the target frameworks).
• Minor and patch updates on the 10.0 line still arrive as one pull request through the existing microsoft-extensions-http group. Bump Microsoft.Extensions.Http and Microsoft.Extensions.Options #121 will be closed once this is merged.

Verification

• The file still parses as YAML, and parsing it before and after differs only by the new updates[0].ignore list.
• The dependency groups in the published DependencyInjection nuspec are net10.0 only, with Microsoft.Extensions.Http and Microsoft.Extensions.Options at 10.0.14.
• Not checked: how Dependabot reads the entry shows only after merge, in the update job that a configuration change starts.

🤖 Generated with Claude Code