Bump WolverineFx from 5.24.0 to 6.4.1#713
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
--- updated-dependencies: - dependency-name: WolverineFx dependency-version: 6.4.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated WolverineFx from 5.24.0 to 6.4.1.
Release notes
Sourced from WolverineFx's releases.
6.4.1
Just hardening Wolverine against a condition that only happens (we think) in CritterWatch
What's Changed
Full Changelog: JasperFx/wolverine@V6.4.0...V6.4.1
6.4.0
This release was 100% about CritterWatch and does not impact any other functionality
What's Changed
Full Changelog: JasperFx/wolverine@V6.3.2...V6.4.0
6.3.2
What's Changed
Full Changelog: JasperFx/wolverine@V6.3.0...V6.3.2
6.3.0
The top line change here was a lot of work to make Wolverine able to pre-generate code as F# in addition to the existing C# model.
What's Changed
Full Changelog: JasperFx/wolverine@V6.2.2...V6.3.0
6.2.2
Patch release on top of 6.2.1.
🐛 Bug Fixes / Codegen
#2963 (closes #2958): EF Core transaction middleware + post-save cascade flush
The HTTP-handler codegen path under the EF Core transaction middleware + outbox cascade (GH-536) no longer fails handler compilation. Two related codegen issues addressed in this PR:
var messageContextdeclaration in the generated handler. Cherry-picked from #2959, originally authored by @kentcooper — credit preserved on commit9df45bfde. Root cause:MessageBusSourcewas returning a freshCreateMessageContextWithMaybeTenantFrameper call; once cached + always returning the concreteMessageContext, the duplicate goes away.'IMessageContext' does not contain a definition for EnqueueCascadingAsync— surfaced after the cache fix because once the source produced a concreteMessageContextVariable, the downstreamCaptureCascadingMessagesframe still declared itsMethodCalltarget astypeof(IMessageContext)and emitted a bad((IMessageContext)messageContext).EnqueueCascadingAsync(…)cast. Fixed by re-targetingCaptureCascadingMessagesto the concreteMessageContexttype — mirrors the existingFlushOutgoingMessagespattern. Latent insrc/Wolverine/Runtime/Handlers/CaptureCascadingMessages.cssince020e79013e(2022-09-16); the variable-cache fix is what flipped it from masked to visible.📦 Dependency bumps
JasperFx+JasperFx.Events+JasperFx.Events.SourceGenerator+JasperFx.SourceGenerator2.2.1 → 2.2.3JasperFx.RuntimeCompilerunchanged (own 5.x line, stays at 5.0.0)Upstream JasperFx 2.2.2 release: https://github.com/JasperFx/jasperfx/releases/tag/V2.2.2 (
Fix source-created codegen variable reuse, #392). 2.2.3 was a same-day version-bump-only re-roll.📖 Documentation
DeadLetterEnvelopeGetRequest/DeadLetterEnvelopeResults/DeadLetterEnvelopeIdsRequestsignatures — the docs still described the pre-5 cursor-based pagination (StartId/NextId) and the legacyDeadLetterEnvelopesFoundResponsewrapper. Updated for offset-basedPageNumberpagination, the multi-storeIReadOnlyList<DeadLetterEnvelopeResults>response shape, and tenant-awareIdsrequest bodies.🧪 Known issues
SharedMemorytransport does not serialize envelopes on cross-host send. Surfaces as aMartenTests.Distribution.with_ancillary_stores.spread_out_over_multiple_hostsfailure whereAssignAgentsystem commands arrive at the destination node with emptyData/MessageTypeand the receive pipeline can't deserialize them. Long-standing — the marten CI workflow has been red on this test through V6.2.0 and V6.2.1, predates this release line entirely. Unblocked the V6.2.2 cycle by adding[Fact(Skip = "…")]referencing #2965; the underlying serialization bug is tracked separately and is out of scope for a JasperFx pin-bump patch release.Full changelog: JasperFx/wolverine@V6.2.1...V6.2.2
6.2.1
Patch release picking up upstream JasperFx 2.2.1 fixes. No Wolverine code changes — pure dependency bump.
Bumped pins
JasperFxJasperFx.EventsJasperFx.Events.SourceGeneratorJasperFx.SourceGeneratorUnchanged
JasperFx.RuntimeCompilerRelated links
6.2.0
Bug-fix + feature release on top of 6.1.0 — 13 PRs.
✨ New features
Custom
Result<T>Support — #2952 (refs #2221)First three phases of native
Result<T>-style handler return-value support:ResultPolicyregistry, handler-side unwrapping seams, and caller-sideInvokeAsync<T>unwrap. Lays the groundwork for integrating with libraries likeErrorOr,OneOf,FluentResults, etc.DbContext Abstractions for EF Core Transaction Middleware — #2919, #2954
The EF Core transaction middleware now binds correctly when handler parameters are declared as interface or abstract base abstractions over a concrete
DbContext. Multiple abstractions to the sameDbContextare supported in a single handler — the runtime resolves them all to the same scoped instance, and the transaction still auto-applies.📖 DbContext Abstractions docs
🚀 Performance
Outgoing Envelope Pooling — #2956 (closes #2955)
MessageRouter.RouteForPublishnow acquires from the runtime envelope pool (originally introduced in #2741 for the Executor sites in 6.1.0) when the route's sender is anInlineSendingAgentorBufferedSendingAgent. Measured −504 B/op (−90 %) on the transport-bound publish/send paths in the CritterStackScalability harness, with ~10× fewer Gen0 collections per 1k ops.DurableSendingAgent, local-queue agents, andISenderRequiresCallbacksenders are explicitly excluded — different lifecycle plumbing required, tracked as follow-ups.🐛 Bug fixes
Marten / Polecat
[ReadAggregate]/[DocumentExists]handlers (closes #2941).chain.AncillaryStoreTypein Phase A so the inbox-routing map sees[MartenStore](closes #2944).Persistence (Postgres / MySQL)
PostgresqlQueueidentifiers through Weasel'sPostgresqlIdentifier.Shorten()so long queue names don't overflow Postgres's 63-byte identifier limit (closes #2942).PersistNodeRecordSQL with unquoted schema (MySQL, closes #2940).Pulsar
KeyNotFoundExceptionacking batch messages on partitioned topics (supersedes #2883).Distributed agents
InvokeAsync<T>reply timeout 10 s → 30 s (closes #2949).Quality
📖 Documentation
📦 Dependency bumps
Full changelog: JasperFx/wolverine@V6.1.0...V6.2.0
... (truncated)
6.1.0
Wolverine 6.1.0
Minor release. Critter Stack dependency refresh, plus the rollup of the entire post-6.0.0
6.0.xline — most significantly the AOT runtime-scanning-elimination work and a new command-line handler-discovery diagnostic.Dependencies
9.0.1→9.2.02.1.3→2.2.0(#2938)4.1.1(unchanged — already latest)5.0.0(unchanged — own 5.x line)Marten 9.2.0 now bundles
JasperFx.Events.SourceGeneratoras an analyzer, so projects referencingWolverine.Martenreceive it transitively. The previously-explicit analyzer references were dropped from the 8 Marten-referencing projects to avoid running the generator twice, which produced duplicateEvolve/*Evolverbuild errors (#2939).PolecatTestsretains its explicit reference because Polecat does not bundle the generator.New & Noteworthy
AOT: eliminate runtime assembly scanning — AOT Publishing. Static-mode apps no longer scan assemblies at startup; discovery now flows through source-generated manifests:
[WolverineHandlerModule]assemblies, with no filesystem probe — #2905 / #2935TypeQuery— #2909 / #2932GetTypes()scan — #2908 / #2936Command-line handler-discovery diagnostic — Command Line Integration · Command Line Diagnostics tutorial. New
dotnet run -- wolverine-diagnostics describe-handlers <Type>runsDescribeHandlerMatchfrom the CLI so you can troubleshoot handler discovery without editing your bootstrapping code — #2921 / #2923Build-time OpenAPI generation — Command Line Integration.
dotnet run -- openapigenerates the OpenAPI document without starting the host (no database/broker required) — #2903 / #2911SQS fair queues on standard queues — support
MessageGroupIdon standard Amazon SQS queues — #2886 / #2889SignalR
ClaimsPrincipal— the connection'sClaimsPrincipalis now exposed onSignalREnvelope— #2927 / #2937EF Core transactional outbox timing fix — the EF Core transaction and outbox flush now complete before the HTTP response is written — #2917 / #2920
Mixed-lifetime
IEnumerable<T>support; Lamar removed — handlers depending on a mixed singleton/scopedIEnumerable<T>now resolve every element correctly; Lamar is no longer used or supported, and the built-inServiceProvideris the container — #2896 / #2914Aggregate handler naming clarity — clarified and guarded the
*AggregateHandlernaming convention vs.[ReadAggregate]— #2924Production code-generation guidance — Code Generation. How to drop Roslyn from production images, with a linked
CqrsMinimalApisample — #2900 / #2912Bug fixes
Senderroutes built during description mode — #2897 / #2899What's Changed
... (truncated)
6.0.0
Wolverine 6.0.0 — Critter Stack 2026
The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).
Highlights
net9.0;net10.0.WolverineFxno longer ships Roslyn. Apps in the defaultTypeLoadMode.Dynamicmust addWolverineFx.RuntimeCompilation, or pre-generate viacodegen write+TypeLoadMode.Static(the trimmer then drops Roslyn). See the migration guide.ServiceLocationPolicy.NotAllowedis the default (BREAKING) — restructure registrations, allow-list per type, or callopts.RestoreV5Defaults()to revert.IsAotCompatible=true(except the intentionalWolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.WolverineFx.Newtonsoft/WolverineFx.Http.Newtonsoft;IForwardsTo<T>discovery now explicit; removed[Obsolete]APIs (EventForwardingToWolverine,RedisTransport.BuildRedisStreamUri,PulsarEndpoint.UriFor).Migration guide: https://wolverinefx.net/guide/migration.html (or
docs/guide/migration.md). Master plan: wolverine#2715. Remaining release-cut comms items tracked in #2745.5.39.1
Fixed a regression problem reported here JasperFx/wolverine#2739
Full Changelog: JasperFx/wolverine@V5.39.0...V5.39.1
5.39.0
What's Changed
Fault<T>on Terminal Handler Failure by @BlackChepo in Fault Events — Auto-PublishFault<T>on Terminal Handler Failure JasperFx/wolverine#2695New Contributors
Full Changelog: JasperFx/wolverine@V5.38.0...V5.39.0
5.38.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.2...V5.38.0
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
5.36.1
Upgrade to this version please if you use the EF Core transactional middleware and are using a very recent version of Wolverine
What's Changed
Full Changelog: JasperFx/wolverine@V5.36.0...v5.36.1
5.36.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.35.2...V5.36.0
5.35.2
What's Changed
A small bug-fix and dependency-refresh release.
Persistence fixes
OracleMessageStore.Initializeand the surrounding schema declared timestamp columns (health_check,started,posted, etc.) with a DEFAULT ofSYS_EXTRACT_UTC(SYSTIMESTAMP). That returns a TIMESTAMP without a time zone, and when implicitly cast into theTIMESTAMP WITH TIME ZONEcolumn Oracle stamps it with the session time zone — so for any session in UTC+N the just-persisted value's UTC equivalent was N hours in the past. That tripped theNodeAgentController.DoHealthChecksAsyncstaleness filter and surfaced as aNullReferenceExceptionduring the first leadership-election heartbeat (self!.AssignAgents([LeaderUri])on anullself). All 18 occurrences swapped toSYSTIMESTAMP AT TIME ZONE 'UTC', with quote-doubling for the DDL contexts that go through Weasel'sEXECUTE IMMEDIATE '...'wrapper.Reliability hardening
dbcontrol://andoraclecontrol://endpoints toBufferedInMemory(#2637) — the database-backed control transport carries inter-node leader-election and agent-reassignment commands. Marking either endpoint Durable would route every control envelope through the same store-backed inbox/outbox the durability agent itself owns (deadlock); marking it Inline contradicts the batched-poll semantics. BothDatabaseControlEndpointandOracleControlEndpointnow overridesupportsModeso any policy that tries to flip them offBufferedInMemoryeither silently skips (UseDurableInboxOnAllListeners,UseDurableOutboxOnAllSendingEndpoints, etc., already checkSupportsMode) or fails fast with a clearInvalidOperationException.Source-gen / startup
IWolverineTypeLoaderacross all known assemblies (#2632) by @devployment — since 5.34.0, hosts on the source-generated codegen path silently dropped handlers that lived in referenced assemblies becausetryDiscoverTypeLoaderFromAttributeonly inspectedOptions.ApplicationAssembly. First invocation of one of those handlers threwIndeterminateRoutesException. The runtime now walksApplicationAssemblyand every assembly inDiscovery.Assemblies, collects every[WolverineTypeManifest]loader it finds, and exposes their union via the new internalCompositeWolverineTypeLoader. Existing single-loader semantics are preserved when only one manifest is found.Other
Dependencies
Full Changelog: JasperFx/wolverine@V5.35.1...V5.35.2
5.35.1
What's Changed
A bug-fix and small-feature release covering Oracle-in-Balanced-mode startup, a duplicate-poller defect on RavenDb, an AWS SQS sharded-slot naming fix, and a new SagaDescriptor surface for CritterWatch.
Persistence fixes
Oracle in
DurabilityMode.Balancednow boots (#2622) —OracleMessageStore.Initializewas a no-op, so hosts using Oracle persistence in Balanced mode failed to start withArgumentOutOfRangeException("ControlEndpoint cannot be null for this usage"). The fix mirrorsMessageDatabase.Initializefor Oracle and stands up a parallelOracleControlTransport/OracleControlEndpoint/OracleControlSender/OracleControlListenerset under the neworaclecontrol://protocol — necessary because the sharedDatabaseControlSender/DatabaseControlListenerassume@-prefixed placeholders and Guid values that map directly onto aDbParameter, neither of which Oracle accepts (:-prefixed placeholders,RAW(16)id columns requiringbyte[]). Also fixes a latentOracleMessageStore.EnqueueAsyncno-op that leftLogRecordsAsyncsilently dropping node records, and makesFetchRecentRecordsAsyncDBNull-safe on the description column. Adds a newOracleTests.LeaderElectionproject so the leadership-compliance suite runs against Oracle (marked[Trait("Category","Flaky")]because the suite needs careful TM/DML lock sequencing between back-to-back runs).RavenDb: only one durability agent polls after host start (#2623, #2629) by @Bishbulb (root-cause investigation and original fix) and @jeremydmiller —
RavenDbMessageStore.StartScheduledJobseagerly built and started aRavenDbDurabilityAgentat boot in addition to the agent thatNodeAgentControlleralready builds and starts viaIAgentFamily/MessageStoreCollection. TwoRavenDbDurabilityAgentinstances then polled the same database concurrently, both believed they held the scheduled-job lock, raced to mark the same envelopesIncoming, and surfacedConcurrencyExceptionplus double-fired timeouts. Drops the eagerStartTimers()call; the cluster-managed agent is now the single owner of polling. The agent returned fromStartScheduledJobsis held byWolverineRuntime.DurableScheduledJobspurely for its disposal-timeStopAsync. Comes with a reflection-free regression test (addedRavenDbDurabilityAgent.IsPollingandCompositeAgent.InnerAgentsfor the test to enumerate without poking at private fields). A companion regression-guard test for CosmosDb is included; investigation showed the equivalent CosmosDb path does NOT have the bug today (CosmosDbMessageStore.BuildAgentFamilyreturns null andUriuses thecosmosdb://scheme rather thanwolverinedb://, soMessageStoreCollectionnever registers a competing agent).Other improvements
AWS SQS: correct naming for sharded slot endpoints in #1f294ce5 — fixes a regression where sharded slot endpoint URIs were assembled with the wrong segment ordering, causing the consumer side to listen at the wrong queue.
SagaDescriptorexported viaServiceCapabilitiesin #f0998c7b — adds a saga-shape descriptor (saga type, id type, current state) to the capabilities exporter so CritterWatch can surface saga inventory and current state in its dashboard.Full Changelog: JasperFx/wolverine@V5.34.0...V5.35.1
5.34.0
What's Changed
This release introduces three new features (Claim Check pattern, declarative Polecat data requirements, and a new opt-in
WolverineFx.RuntimeCompilationpackage as the first step toward AOT compatibility), a fix for a long-standing service-location footgun, several real RavenDB and EF Core durability fixes, plus the cold-start prep work done as part of issue #1577.Highlights
[Blob]attribute (#2412) by @jeremydmiller in #2617 — off-load large message-property payloads to external storage on send and re-hydrate them on receive, so the on-the-wire envelope stays small. Core abstractions (IClaimCheckStore,ClaimCheckToken,[Blob],FileSystemClaimCheckStore,opts.UseClaimCheck(...)) live inWolverine.Persistence. Two new backend NuGet packages ship alongside:WolverineFx.ClaimCheck.AzureBlobStorageandWolverineFx.ClaimCheck.AmazonS3. New documentation page under/guide/durability/claim-checks.[DocumentExists<T>],[DocumentDoesNotExist<T>], andPolecatOps.Document<T>().MustExist(...)/.MustNotExist(...)mirror the Marten ergonomics, with the same batch-query optimization that folds multiple existence checks into a single PolecatIBatchedQueryround-trip.IMessageBus/IMessageContextnow see the active context (#2583) by @jeremydmiller in #2616 — when user code service-locatesIMessageBus(e.g., constructor injection on a service the handler resolves at runtime), it now receives the sameMessageContextthe handler itself uses, preserving outbox semantics. Implemented as a per-chain opt-in (gated onChain.UsesServiceLocation) so chains that don't service-locate pay zeroAsyncLocaloverhead per message.WolverineFx.RuntimeCompilationopt-in package (#1577) by @jeremydmiller in #2613 and #cc00ca0a — first pass at the cold-start / AOT roadmap. Wires theWolverine.SourceGenerationanalyzer into theWolverineFxNuGet output (so source-generatedIWolverineTypeLoaderdiscovery flows transitively to consumers), pre-populates theWolverineMessageNamingcache during startup to eliminate first-message reflection cost, applies[DynamicallyAccessedMembers]annotations on theActivator.CreateInstancecall sites for trimmer-friendliness, and addsConfigureAwait(false)across 117 awaits on the per-message hot path. The newWolverineFx.RuntimeCompilationpackage becomes the future-facing opt-in API for runtime Roslyn compilation; default behavior is preserved.RavenDB durability fixes
EF Core / ancillary stores
DurableLocalQueueto route incoming envelopes to ancillary stores (#2611) by @jeremydmiller — handler chains targeting an ancillary message store now have their incoming envelopes persisted in that store rather than the main store, fixing a class of "envelope stuck as Incoming forever" bugs.WolverineEnabledannotation collision in ancillary-store EF Core scenarios as part of #2618 —MapWolverineEnvelopeStorageis now idempotent when called against the same model graph more than once.Other improvements
MessageBusclobbering per-messageEnvelope.Sourcein #26e38002 —MessageBus.Sendwas overwriting the per-messageSourcewith the host'sServiceName, masking the originating service in causation tracking.ServiceLocationPolicy.NotAllowedv6 default (#2584) by @jeremydmiller in #2609 — chains that resolve dependencies via service location now log a warning at codegen time, with a clear migration path to the new opt-inWolverine.RuntimeCompilationstory for v6.CI stabilization
IDisposable→IAsyncLifetimeconversions, lifecycle cleanup; chronically broken-on-CI classes (SqliteTests.Transport.multi_tenancy_with_multiple_files,CosmosDbTests.LeaderElection.leader_election,Wolverine.RabbitMQ.Tests.send_by_topics,Wolverine.RabbitMQ.Tests.sending_raw_messages) tagged[Trait("Category", "Flaky")]with header comments documenting the symptom and the real follow-up fix.JasperFx.CodeGenerationandJasperFx.RuntimeCompilernow compile cleanly after theInitializeSynchronouslyextension method was moved intoJasperFx.CodeGenerationupstream.Issue-tracker housekeeping
#2507(Quartz.Net / TickerQ first-class integration) added to the 6.0 milestone with a phased plan documented on the issue.#1577(cold-start optimization roadmap) updated with a six-phase plan and current-state checklist; phases 1–4 are non-breaking on v5.x and largely landed in this release.Full Changelog: JasperFx/wolverine@V5.33.0...V5.34.0
5.33.0
What's Changed
This release includes a major reliability fix for distributed leader election, a port of the Polecat 2.x event store integration, and several other quality-of-life improvements.
Highlights
LeadershipLostnode record type and anIWolverineObserver.LostLeadership()hook for monitoring.JSONtype.Other Improvements
launchSettings.jsonto sample projects by @jeremydmiller in #2600Full Changelog: JasperFx/wolverine@V5.32.1...V5.33.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.32.1...V5.33.0
5.32.1
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.32.0...V5.32.1
5.32.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.31.1...V5.32.0
5.31.1
What's Changed
Full Changelog: JasperFx/wolverine@V5.31.0...V5.31.1
5.31.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.30.0...V5.31.0
5.30.0
This release is mostly about CritterWatch or the new AI skills usage with a few housekeeping issues
What's Changed
Full Changelog: JasperFx/wolverine@V5.29.0...V5.30.0
5.29.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.28.0...V5.29.0
5.28.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.27.0...V5.28.0
5.27.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.26.0...V5.27.0
5.26.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.25.0...V5.26.0
5.25.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.24.0...V5.25.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)