[AdCodicem]

What changed

The repository went from 12 to 38 packages in two weeks. This pull request:

• lands the fixes the measurements already settle;
• records, as two accepted ADRs, how the packages are versioned and checked from now on.

Nothing in it releases anything: only ci, docs(adr) and docs commits. It is rebased on main, which now carries #192.

ci(deps): Dependabot (.github/dependabot.yml, docs/maintaining.md)

• Every shipped dependency's major is now ignored. 23 of the 44 in .github/shipped-dependencies had no ignore. Test-only packages of the same families move with them.
• Microsoft.CodeAnalysis.CSharp* ignores its minors too. Its major.minor is the oldest compiler that loads the generator, since an analyzer referencing a later Microsoft.CodeAnalysis fails with CS9057 (fix(deps)!: Bump Microsoft.CodeAnalysis.CSharp from 4.14.0 to 5.9.0 #190, closed).
• xunit.v3*, Microsoft.CodeAnalysis*, HotChocolate* and ModelContextProtocol* require one another at exactly one version. Each family now updates in a group of its own, ahead of dotnet, so that a red family holds back no other update. fix(deps): Bump the dotnet group with 10 updates #189 was one; fix(deps): take the xunit.v3 family at 4.0.2 and FluentValidation 12.2.0, in place of #189 #192 replaced it.

ci: concurrency (ci.yml, lint.yml)

• A push to a pull request cancels the run it supersedes. That was 13 % of pull-request job-minutes.
• A push to main is never cancelled.
• The workflow's name is in the key, so that ci and lint never cancel each other.

docs(adr): ADR 0012, accepted. The packages are versioned in two trains, independently of the frameworks.

• The core train goes to 1.0 on its own: the generator, Abstractions, Json, Identifiers, Testing.Data and the five Microsoft integrations.
• The 28 satellites stay 0.x together, reach 1.0 together, then may leave in families.
• Every dependency on one of our packages is bounded [V, next breaking version), and the core is released first.
• A framework's major is supported in the same packages, train by train, with no maintenance line and no version aligned with a framework's.
• The contract kit splits into a framework-free Testing.Contracts in the core and the existing Testing as a thin xunit adapter.
• It supersedes ADR 0010.

docs(adr): ADR 0013, accepted. A pull-request CI targeted by package family, with the heavy jobs before a release.

• Eleven CI families, each in one train, are picked by a plan that crosses the diff with dotnet-affected. At every run, the plan checks that each project and each unit-test folder belongs to exactly one family.
• Phase A filters the one unit-test assembly by family. Phase B splits it into a test project per family, which amends ADR 0006.
• build and test becomes the one required aggregator.
• native AOT, native AOT (Marten), the integration suite and compat (.NET 11) move to a reusable heavy.yml. It gates every preview and stable release, and runs after each push to main.
• Codecov gets one flag per family, with carry-forward.

Statuses and documents

• ADR 0010 is marked superseded. The statuses of ADRs 0003, 0005, 0006 and 0009 record their amendments.
• The root CLAUDE.md says that both ADRs are accepted but not built yet, so that agents keep to the current mechanics until the roadmap lands.
• Every document that planned for compat (.NET 11) or native AOT (Marten) to become a required check now says that neither will:
  • the root, .github and tests/Compat CLAUDE.md files;
  • the runbook;
  • two comments in ci.yml.

Checklist

• Unit and generator suites: not run locally for this pull request. No code changes, and no test reads the changed files (grep over tests/ finds them only in comments). CI runs both suites.
• Codecov: no code changes. Codecov reports all modified coverable lines covered.
• Consumer surface: unchanged.
• Diagnostics: none added.
• Benchmarks: no claim touched.
• 7 commits (git rev-list --count origin/main..HEAD).

Also checked:

• actionlint 1.7.12, the version lint.yml pins, passes on every workflow.
• Every commit message passes the pinned conventional-pre-commit.
• All 44 shipped dependencies match a major ignore.

🤖 Generated with Claude Code

https://claude.ai/code/session_0164hf4jJ3KsP3tyC3Uoa55L

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[AdCodicem]

compat (.NET 11) failed on b02e9c1 (run 39314175776, since superseded): the six MongoDbTests could not start their mongo:8.0 container.

MongoDB cannot start: Linux kernel versions 6.19 and newer has a known incompatibility with this version of MongoDB. See https://jira.mongodb.org/browse/SERVER-121912

Not this pull request's. It changes no code, no test and no image. The job landed on the runner image ubuntu-24.04 20261018.339.1, whose kernel is 6.19 or later, and every MongoDB 8.x refuses to start there.

• build and test passed its MongoDB integration tests on the same commit, on a runner with an older kernel. Which job fails depends on the runner a job lands on.
• That puts the integration suite in build and test, a required check, at risk on every pull request and on main too, as the new image rolls out.

No fix exists yet.

• MongoDB's ticket names no fixed version. Reports from 2026-10-14 have 8.0.34 and 8.3.13 still refusing, while 7.0.45 starts.
• The GLIBC_TUNABLES workarounds are reported not to help.
• Moving both fixtures (tests/AdCodicem.ValueObjects.IntegrationTests/Fixtures/MongoDbFixture.cs, tests/Compat/MongoDbTests.cs) to mongo:7.0 would start. But MongoDbValidatorTests pins MongoDB 8.0's PCRE2 behaviour, and the README's support table promises MongoDB 8. That choice is the maintainer's, so it is not widened into this pull request.

The run on the current head, bd4d12e, is in progress and is the re-run.

---

Generated by Claude Code