chore(deps): Bump WolverineFx from 6.0.2 to 6.4.1#70
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
--- updated-dependencies: - dependency-name: WolverineFx dependency-version: 6.4.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
.NET
Contributor
Author
|
Superseded by #72. |
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
1 participant
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 6.0.2 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)
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)