Repository navigation
Bump WolverineFx and WolverineFx.FluentValidation - #12
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps WolverineFx from 6.61.0 to 6.62.0 Bumps WolverineFx.FluentValidation from 6.60.0 to 6.62.0 --- updated-dependencies: - dependency-name: WolverineFx dependency-version: 6.62.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: WolverineFx.FluentValidation dependency-version: 6.62.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Nov 6, 2026
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 6.61.0 to 6.62.0.
Release notes
Sourced from WolverineFx's releases.
6.62.0
This is a minor release on JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0 and Fisher 1.28.0. Upgrading is a package bump: there is no schema change and no breaking API change. If your projects pin
JasperFx.Events.SourceGeneratorcentrally, pin it to the same version asJasperFx.Events(see the note at the end).New
[SagaIsResponseOnly]for an endpoint that returns a saga as its response (GH-5069).PublishOnlyToShardedPostgresqlQueues, for publishing to sharded queues with no listeners (GH-5088).AggregateExceptionof concurrency failures maps to 409 (GH-5355);[DeduplicatedWithResponse]replays ASP.NET CoreIResultresponses, and reads a replayedLocationwithout per-request reflection (GH-5381).kafka-replay --group-idoption (thanks to new contributor @Mr444-dev).WhenTrackedsees events an application commits through its own injectedIDocumentSession, on Marten, Polecat and Fisher (GH-5385, GH-5390);GenerationRules.ReuseCompiledAssemblies(JasperFx 2.100.0) is documented and tested for many hosts in one process, in Dynamic and Auto modes, the codegen command and HTTP chains (GH-5378, GH-5391).EventModelReportprints the decider line beside starts (GH-5379), andscaffoldturns a multi-event automation into one handler class (GH-5361).Fixes
DurableLocalQueue.StartAsyncskips an already accepting queue and is serialized (GH-5348).ListenerCount > 1no longer recurses forever (GH-5363).OnExceptionreturning a tuple generates code that compiles (GH-5356), andOnExceptionhandlers for the same exception type merge into one catch clause.CloudEventsMapperkeeps the envelope id on re-read, with a stable id for non-Guid CloudEvent ids (GH-5364).Applyon every stream (GH-5360, a partial fix; the rest stays open).Microsoft.DotNet.ILCompileris cleared (GH-5387).Pinning JasperFx centrally
Polecat 5.49.0 needs JasperFx 2.100.1. If
JasperFx.Eventsis lifted to 2.100.1 whileJasperFx.Events.SourceGeneratorstays pinned at 2.100.0, the generator emits nothing and projections fail at run time with "No source-generated dispatcher found". Keep the two on one version (jasperfx#1138).What's Changed
... (truncated)
Commits viewable in compare view.
Updated WolverineFx.FluentValidation from 6.60.0 to 6.62.0.
Release notes
Sourced from WolverineFx.FluentValidation's releases.
6.62.0
This is a minor release on JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0 and Fisher 1.28.0. Upgrading is a package bump: there is no schema change and no breaking API change. If your projects pin
JasperFx.Events.SourceGeneratorcentrally, pin it to the same version asJasperFx.Events(see the note at the end).New
[SagaIsResponseOnly]for an endpoint that returns a saga as its response (GH-5069).PublishOnlyToShardedPostgresqlQueues, for publishing to sharded queues with no listeners (GH-5088).AggregateExceptionof concurrency failures maps to 409 (GH-5355);[DeduplicatedWithResponse]replays ASP.NET CoreIResultresponses, and reads a replayedLocationwithout per-request reflection (GH-5381).kafka-replay --group-idoption (thanks to new contributor @Mr444-dev).WhenTrackedsees events an application commits through its own injectedIDocumentSession, on Marten, Polecat and Fisher (GH-5385, GH-5390);GenerationRules.ReuseCompiledAssemblies(JasperFx 2.100.0) is documented and tested for many hosts in one process, in Dynamic and Auto modes, the codegen command and HTTP chains (GH-5378, GH-5391).EventModelReportprints the decider line beside starts (GH-5379), andscaffoldturns a multi-event automation into one handler class (GH-5361).Fixes
DurableLocalQueue.StartAsyncskips an already accepting queue and is serialized (GH-5348).ListenerCount > 1no longer recurses forever (GH-5363).OnExceptionreturning a tuple generates code that compiles (GH-5356), andOnExceptionhandlers for the same exception type merge into one catch clause.CloudEventsMapperkeeps the envelope id on re-read, with a stable id for non-Guid CloudEvent ids (GH-5364).Applyon every stream (GH-5360, a partial fix; the rest stays open).Microsoft.DotNet.ILCompileris cleared (GH-5387).Pinning JasperFx centrally
Polecat 5.49.0 needs JasperFx 2.100.1. If
JasperFx.Eventsis lifted to 2.100.1 whileJasperFx.Events.SourceGeneratorstays pinned at 2.100.0, the generator emits nothing and projections fail at run time with "No source-generated dispatcher found". Keep the two on one version (jasperfx#1138).What's Changed
... (truncated)
6.61.0
This is a minor release. Upgrading is a package bump only: there is no schema change and no breaking API change.
New
CronSchedule.MinimumCadenceis now one second, for six-field cron expressions such as* * * * * *. Anything faster than five seconds always runs on a timer agent, andUseScheduledMessages()refuses it.SkipWhileRunning()on a recurring schedule invokes each occurrence instead of publishing it. An occurrence that comes due while the previous one is still running is skipped, and skipped occurrences are not made up later. Skips are logged and counted in the newwolverine-recurring-occurrences-skippedmetric.PauseThenCatchUpOnAllMartenDaemonActivityAsync()and the tracked-session optionPauseThenCatchUpOnAllMartenDaemonActivity()catch up the main Marten store and every ancillary store registered withIntegrateWithWolverine()in one call. A store with no events is skipped.exceptionevent (exception.type,exception.message,exception.stacktrace) on its span, instead of only the exception's type name. Exception messages can carry application data, so you can turn this off withopts.Tracking.RecordExceptionsOnSpans = false.EntityDescriptor.Ddlnow carries each EF Core entity'sCREATE TABLEscript, with its keys, foreign keys and indexes, the same wayDocumentMappingDescriptor.Ddldoes for documents. It's generated from the model, so no connection is opened, and it's the model's script rather than the database's. Non-relational providers and view-mapped entities leave it empty. Needs JasperFx 2.99.0.http.routeandhttp.request.method, the OpenTelemetry semantic convention names, alongsidehandler.type. Both are constants in the generated code. Pre-generated code should be regenerated.DeadLetterEnvelopeQuery.RangeOn(DeadLetterTimeField.SentAtorFailedAt) (#5330).FailedAtfalls back tosent_atwhenfailed_atis null, and applies to query, replay, discard and archive. The default staysSentAt. Supported by the PostgreSQL, SQL Server, MySQL, SQLite, Oracle, CosmosDb and RavenDb stores.Fixes
TrackConnectionsturned on, the handler, saga and stream tags (handler.type,message.handler,wolverine.saga.*,wolverine.stream.*) landed on themarten.connectionspan instead of the message's own span. They now stay on the message span, and on the request span for HTTP endpoints. Pre-generated code should be regenerated.ScheduleRetry(...)lost the link to the attempt that failed, because the stored envelope body wasn't rewritten when the retry was scheduled. Every message store now rewrites the body when it reschedules an envelope.DeadLetterStorageMode.NativeWithRecoverywhenEnableDeadLetterQueueRecovery()drains them, so CritterWatch's startup check no longer warns about them.EnableDeadLetterQueueRecovery(), stopping the host could throwAlreadyClosedExceptionwhen two stops ran at once, as they do underWebApplicationFactory. Stopping the dead letter queue listener is now idempotent and never throws.FindSingleTrackedMessageOfType<T>()now counts envelopes rather than distinct message values, so publishing two equal records fails the check. A message sent to several destinations still counts once. Usetracked.Sent.SingleMessage<T>()for a check per destination.PauseThenCatchUpOnMartenDaemonActivitywaits out the high water agent's current poll tick. The fix is JasperFx/jasperfx#1100.ServiceCapabilities.Sagasonce it had been handled, and the saga disappeared once every message had been. The saga report, including each store'sGetRegisteredSagasAsync, now reads the same before and after the chains compile.Balancedmode, lifting a pause on a URI that no agent owns, such as a listening endpoint, waited outAgentRestrictionConfirmationTimeoutand then threwAgentRestrictionsNotConfirmedException. It now returns at once. Agent URIs are still confirmed as before.IPolecatOutbox.EnrollorIFisherOutbox.Enrollnever flushed their outgoing messages on commit (#5309). Durable messages waited until a restart and buffered messages were lost. They now flush on commit, the same as handler sessions, and the incoming envelope is marked handled once instead of twice.Dependencies
WolverineFx.MySql. On SQL Server, aDateTimeparameter in a message store command now goes out asdatetime2instead ofdatetime. Every envelope time column isdatetimeoffset, so no column is converted either way.Thanks to @uniquelau for #5313, #5314, #5315, #5317 and #5318, and to @lahma for #5330.
Full Changelog: JasperFx/wolverine@V6.60.0...V6.61.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)