Skip to content

ci(deps): keep the NuGet block to options NuGet supports - #100

Merged
bgard68 merged 1 commit into
mainfrom
fix/dependabot-config-nuget-options
Aug 31, 2026
Merged

ci(deps): keep the NuGet block to options NuGet supports#100
bgard68 merged 1 commit into
mainfrom
fix/dependabot-config-nuget-options

Conversation

@bgard68

@bgard68 bgard68 commented Aug 31, 2026

Copy link
Copy Markdown
Owner

What's wrong

.github/dependabot.yml has not been in effect since 2026-08-07. Dependabot rejects it, falls back to the last configuration that parsed, and reports nothing on the pull requests it goes on opening.

The evidence is in the PR titles themselves. Commit 1c7f66b (2026-08-07) renamed the NuGet group dotnet-minor-patchdotnet-production/dotnet-development and changed the Actions prefix chore(ci)ci(deps). Every Dependabot PR opened since still uses the old names:

Date PR Title Config says
08-10 #36 chore(deps): Bump the dotnet-minor-patch group… dotnet-production
08-17 #49 chore(deps): Bump the dotnet-minor-patch group… dotnet-production
08-24 #73 chore(deps): Bump the dotnet-minor-patch group… dotnet-production
08-31 #97 chore(deps): Bump the dotnet-minor-patch group… dotnet-production
08-31 #99 chore(ci): bump github/codeql-action/init… ci(deps)

For contrast, DevSecOpsSentinel's config is applied — its PRs say "in the github-actions group", matching its file. This repo's don't.

Why it matters

The codeql-action group added on 2026-08-24 (#76) exists precisely to stop init and analyze being proposed separately, because a split bump fails at run time:

Loaded a configuration file for version '4.37.9', but running version '4.37.7'

That group has never applied. #99 and #95 arrived split again this week and both failed exactly that way — the fourth week running (#34/#35, #47/#48, #69/#72, #95/#99).

The fix

commit-message.prefix-development and groups.*.dependency-type are documented as "Supported by: bundler, composer, mix, maven, npm, and pip" — ecosystems with a production/development distinction. NuGet has none, so both are invalid there, and one invalid key invalidates the whole file, not just its block. versioning-strategy landed in the same commit and NuGet is not among its supported ecosystems either.

  • Removed versioning-strategy, prefix-development, and the two dependency-type groups from the NuGet block only.
  • The npm block keeps all three — npm supports them.
  • dotnet-production + dotnet-development collapse into one dotnet-version-updates minor+patch group, which is what they amounted to without the split.
  • dotnet-security, the Microsoft.OpenApi ignore, and the codeql-action/artifact-actions groups are untouched.

Verified the result parses and that no unsupported key remains in the NuGet block.

Note

The Dependabot config-error banner (Insights → Dependency graph → Dependabot) names the exact rejected key. Worth checking it after this merges to confirm the file is accepted — if a banner is still shown, something else in here is also rejected.

Once this is in, the next Monday run should produce a single codeql-action group PR instead of a split pair.

commit-message.prefix-development and groups.*.dependency-type are documented
for bundler, composer, mix, maven, npm and pip -- ecosystems with a
production/development split. NuGet has none, so both are rejected, and a
rejected key invalidates the whole file rather than the one block. Dependabot
went on running the last configuration that parsed, which is why every
Dependabot pull request since 2026-08-07 still carries the group names and
commit prefixes this file stopped using that day (dotnet-minor-patch,
chore(ci)), and why the codeql-action grouping added on 2026-08-24 never
grouped anything: init and analyze kept arriving as two pull requests that
fail with 'Loaded a configuration file for version X, but running version Y'.

versioning-strategy goes with them; it landed in the same commit and NuGet is
not among its supported ecosystems either.

The production/development split cannot be expressed for NuGet, so the two
groups collapse into one minor+patch group, which is what they amounted to.
@bgard68
bgard68 merged commit 4986e45 into main Aug 31, 2026
9 checks passed
bgard68 added a commit that referenced this pull request Aug 31, 2026
Restores the bump from #97, which Dependabot closed unmerged when #100
renamed the dotnet-minor-patch group it belonged to. The change is the
same single patch version #97 carried, and that pull request had already
passed the full suite before it was closed.
bgard68 added a commit that referenced this pull request Aug 31, 2026
Restores the bump from #97, which Dependabot closed unmerged when #100
renamed the dotnet-minor-patch group it belonged to. The change is the
same single patch version #97 carried, and that pull request had already
passed the full suite before it was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant