Migrating from Wolverine 5 to Wolverine 6 New in 1.4.0
Migrate a .NET application from Wolverine 5 to Wolverine 6 (Critter Stack 2026). Covers the WolverineFx.RuntimeCompilation runtime-codegen decoupling (Dynamic mode now throws at startup unless the package is referenced), the ServiceLocationPolicy.NotAllowed default flip with RestoreV5Defaults(), the JasperFx 2.0 / Marten 9 / Polecat 4 dependency line, the WolverineFx.Newtonsoft + WolverineFx.Http.Newtonsoft package extractions, explicit IForwardsTo registration, removed [Obsolete] APIs (EventForwardingToWolverine, RedisTransport/PulsarEndpoint helpers), namespace moves (SnapshotLifecycle, OperationRole), and AOT/Static-mode codegen.
Use when upgrading a Wolverine 5.x codebase to Wolverine 6.0.
Skill details
- Skill name:
wolverine-migration-v5-to-v6 - Applies to:
wolverine - Tags:
migration,wolverine,wolverine-6,critter-stack-2026,upgrade,breaking-changes - Added in: 1.4.0
- License: Proprietary. Copyright JasperFx Software LLC.