diff --git a/src/dotnet/Common/BuildingBlocks.EventDispatcher/BuildingBlocks.EventDispatcher.csproj b/src/dotnet/Common/BuildingBlocks.EventDispatcher/BuildingBlocks.EventDispatcher.csproj index 053c4e95..2b8c9283 100644 --- a/src/dotnet/Common/BuildingBlocks.EventDispatcher/BuildingBlocks.EventDispatcher.csproj +++ b/src/dotnet/Common/BuildingBlocks.EventDispatcher/BuildingBlocks.EventDispatcher.csproj @@ -5,7 +5,9 @@ - + + diff --git a/src/dotnet/Directory.Packages.props b/src/dotnet/Directory.Packages.props index 7905fef4..d4751968 100644 --- a/src/dotnet/Directory.Packages.props +++ b/src/dotnet/Directory.Packages.props @@ -38,10 +38,20 @@ - - - + Gotchas: the maintainers' 'critter-stack-2026' engineering note. + 9.8 → 9.11 (Wolverine 6.9 → 6.16): a partial bump that stays BELOW the + 9.12 regression. Marten 9.12 broke async-projection catch-up under + MasterTableTenancy (which modgud uses) — identity read-models never + materialize — via the JasperFx.Events 2.18 "DI-projection partial-class + dispatch" refactor; still unfixed in 9.16.1 (verified: 41/517 integration + failures). 9.11.0 is the highest known-good (AppTemplate pins it too). + WolverineFx.Marten 6.16 is the last 6.x that pins Marten 9.11 (6.17 jumps + to 9.14). Do NOT lift Marten past 9.11 without running the integration + suite — it provisions per-realm DBs and asserts on projected read-models, + so the regression fails it. --> + + + - + - - + + @@ -64,12 +75,12 @@ - - - - - - + + + + + + @@ -90,12 +101,12 @@ - - - - - - + + + + + +