chore(deps): ignore WolverineFx major-version bumps until 6.0 migration is scoped

[emeraldleaf]

Summary

Adds an `ignore` rule to `.github/dependabot.yml` so Dependabot stops opening weekly PRs that bump WolverineFx to a major version we can't take.

Why

PR #34 (WolverineFx 5.36.2 → 6.0.2) fails every integration test at host startup:

```
System.InvalidOperationException: Wolverine is running in TypeLoadMode.Dynamic,
which compiles handler/middleware code at runtime, but no IAssemblyGenerator (Roslyn) is registered.
Core WolverineFx no longer ships the runtime compiler.
```

Wolverine 6.0 split the runtime code generator out of core (GH-2876). The fix is one of:

• Add `WolverineFx.RuntimeCompilation` as a package reference (auto-registers, simplest)
• Pre-generate via `dotnet run -- codegen write` + `opts.CodeGeneration.TypeLoadMode = TypeLoadMode.Static` (recommended for production)

Neither is a Dependabot pickup. A 5.x → 6.x migration needs its own PR: read release notes end-to-end, restructure, verify the saga + outbox + AddConcurrencyRetry paths still behave. Until then, this rule prevents the weekly noise.

What this changes

• WolverineFx* major-version bumps are ignored. 5.x patches and minors still come through the existing `wolverine` group.
• Pattern is extensible — add other packages here when their majors break the build under a Dependabot rebase.

Follow-up

• Close Bump WolverineFx and 5 others #34 with a pointer to this PR
• Track "Wolverine 6.0 migration" as a future dedicated effort (open issue when ready)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated dependency management configuration to improve stability and reduce unnecessary update notifications.

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 26988bd5-b5a1-42bf-bbcd-c88f53061e7f

📥 Commits

Reviewing files that changed from the base of the PR and between f114811 and 4f63d7c.

📒 Files selected for processing (1)

• .github/dependabot.yml

---

Walkthrough

Dependabot configuration for NuGet now adds an ignore rule that suppresses semver-major version updates for packages matching WolverineFx*. Inline comments document that major version bumps for Wolverine are deferred due to breaking changes in the 6.0 runtime code generator split.

Changes

Wolverine 6.0 Dependabot Configuration

Layer / File(s)	Summary
Suppress major version updates for WolverineFx packages .github/dependabot.yml	Within the NuGet ecosystem updates entry, Dependabot is configured to ignore semver-major version updates for dependencies matching WolverineFx*, with inline comments documenting the deferral of major bumps due to breaking changes in the Wolverine 6.0 runtime code generator split.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues check	❓ Inconclusive	This PR is a preparatory step for issue #34 by deferring major-version updates, but does not directly implement the migration requirements (compilation, breaking changes, testing) outlined in the linked issue.	Clarify whether this PR is intended to fully address issue #34 or serve as a prerequisite; if the latter, ensure issue #34 remains open and tracked for the actual migration work.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title accurately describes the main change: adding Dependabot ignore rules for WolverineFx major-version bumps until the 6.0 migration is properly scoped.
Out of Scope Changes check	✅ Passed	The change is narrowly focused on Dependabot configuration and directly supports the PR objectives of deferring WolverineFx major-version bumps; no out-of-scope changes detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/dependabot-ignore-wolverine-majors

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!