Repository navigation
Bump the patch-und-minor group with 12 updates - #28
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Anthropic from 12.58.0 to 12.60.0 Bumps Aspire.Hosting.JavaScript from 13.6.4 to 13.6.5 Bumps AspNet.Security.OAuth.Apple from 10.0.0 to 10.1.0 Bumps Avalonia from 12.1.4 to 12.1.6 Bumps Avalonia.Controls.WebView from 12.1.1 to 12.1.2 Bumps MailKit from 4.18.1 to 4.18.2 Bumps Microsoft.AspNetCore.Authentication.Google from 10.0.13 to 10.0.15 Bumps Microsoft.EntityFrameworkCore.Design from 10.0.13 to 10.0.15 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.1 to 1.21.0 Bumps QRCoder from 1.8.0 to 1.8.1 Bumps WolverineFx from 6.51.2 to 6.64.0 Bumps xunit.v3 from 4.0.2 to 4.0.3 --- updated-dependencies: - dependency-name: Anthropic dependency-version: 12.60.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-und-minor - dependency-name: Aspire.Hosting.JavaScript dependency-version: 13.6.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: AspNet.Security.OAuth.Apple dependency-version: 10.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-und-minor - dependency-name: Avalonia dependency-version: 12.1.6 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: Avalonia.Controls.WebView dependency-version: 12.1.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: MailKit dependency-version: 4.18.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: Microsoft.AspNetCore.Authentication.Google dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: Microsoft.EntityFrameworkCore.Design dependency-version: 10.0.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-und-minor - dependency-name: QRCoder dependency-version: 1.8.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor - dependency-name: WolverineFx dependency-version: 6.64.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: patch-und-minor - dependency-name: xunit.v3 dependency-version: 4.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: patch-und-minor ... Signed-off-by: dependabot[bot] <support@github.com>
This was referenced Nov 16, 2026
Owner
|
Überholt: Alle zwölf Zielversionen stehen seit #113 auf |
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updated Anthropic from 12.58.0 to 12.60.0.
Updated Aspire.Hosting.JavaScript from 13.6.4 to 13.6.5.
Release notes
Sourced from Aspire.Hosting.JavaScript's releases.
13.6.5
What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.
🐛 Fixes
🖥️ Dashboard authentication is enforced on missing and unauthorized routes — Secured dashboards now check authorization before rendering the main layout for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization; unsecured mode is unchanged. (#22071, 0b6bfe2, @jamesnk)
🔒 Container telemetry no longer implicitly exposes the dashboard frontend — When the Aspire container tunnel is enabled, automatic dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged. (#22071, f017f66, @karolz-ms)
🔒 CLI-generated builds and SDK working directories are isolated — Generated AppHost server and integration builds now ignore automatic MSBuild response files without changing user-authored builds or support for explicitly supplied response files. The
aspire sdk generate,aspire sdk dump, andaspire sdk exportcommands use isolated working directories under<ASPIRE_HOME>/tmp/sdk/<unique-id>, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged. (#22071, 1ecd7cc, @sebastienros)🔒 Agent setup no longer writes configuration content to a shared temporary log —
aspire agent initstops writing agent configuration paths, configuration content, and scan diagnostics toaspire-deprecated-scan.login the operating system's temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update. (#22071, c408ec5, @mitchdenny)🛠️ Updated .NET runtimes and dependencies for startup reliability — Refreshes bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to Native AOT process startup. (#21348, @joperezr)
Full Changelog: v13.6.4...v13.6.5
Full commit: b33d222049f1ecc3bc7257ec07b622fe550b2580
Commits viewable in compare view.
Updated AspNet.Security.OAuth.Apple from 10.0.0 to 10.1.0.
Release notes
Sourced from AspNet.Security.OAuth.Apple's releases.
10.1.0
What's Changed
service_tokensupport for confidential VK ID applications by @diamantove in Add service_token support for confidential VK ID applications aspnet-contrib/AspNet.Security.OAuth.Providers#1278New Contributors
Full Changelog: aspnet-contrib/AspNet.Security.OAuth.Providers@10.0.0...10.1.0
Commits viewable in compare view.
Updated Avalonia from 12.1.4 to 12.1.6.
Release notes
Sourced from Avalonia's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Avalonia.Controls.WebView from 12.1.1 to 12.1.2.
Updated MailKit from 4.18.1 to 4.18.2.
Release notes
Sourced from MailKit's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Authentication.Google from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.AspNetCore.Authentication.Google's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.EntityFrameworkCore.Design from 10.0.13 to 10.0.15.
Release notes
Sourced from Microsoft.EntityFrameworkCore.Design's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
(#8053)
Fixed
PeriodicExportingMetricReadernot making its final collection whenShutdown()was called before its background task had started running onplatforms where threading is not available, such as browsers.
(#8053)
... (truncated)
1.21.0-rc.1
The following changes are from the previous release 1.20.1.
NuGet: OpenTelemetry v1.21.0-rc.1
Fixed a race in the self-diagnostics sink dispatcher where disposing it
while its pump thread was exiting could throw
ArgumentNullExceptionon.NET Framework.
(#7983)
SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.(#8008)
Fixed a race where collecting a metric with delta temporality concurrently
with the creation of a new
MetricPointcould reclaim theMetricPointwhile it was being created, losing the measurement.
(#8019)
Fixed a race where collecting a metric with delta temporality could export
the same series twice in a single collection.
(#8019)
Fixed wildcard matching timeouts that could prevent configured source, meter,
legacy activity, or metric view patterns from matching.
(#8014)
The timeout passed to
MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter instead ofbeing ignored once the export has started, so that the OTLP exporter can
cancel an export which runs past the timeout. The
ExportTimeoutMillisecondsof
PeriodicExportingMetricReadernow also limits exports which are notstarted by the reader itself, such as those of
MeterProvider.ForceFlush().(#7996)
Fixed a race where collecting a cumulative metric concurrently with the
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, could case a
NullReferenceExceptionwhen enumeratingTags.(#8018)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Added support for enabling
ActivitySources from configuration using theMicrosoft.Extensions.Diagnosticstracing APIs introduced in .NET 11 (forexample,
services.AddTracing(b => b.AddConfiguration(section))).... (truncated)
1.21.0-beta.1
The following changes are from the previous release 1.20.1-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1
Fixed OpenMetrics scrape responses containing a
# UNITline whose unit isnot an underscore-separated suffix of the metric family name (for example
auth.failedloginswith the unitlogins), which caused scrapers such asPrometheus to reject the whole response. The
# UNITline is now omittedfor such metrics; exported metric names are unchanged.
(#7993)
Fixed scrapes that negotiate different response formats within the
ScrapeResponseCacheDurationMillisecondswindow each triggering their ownmetrics collection. A collection now also writes the response for other
formats whose scrapes arrived alongside a previous collection, so scrapes
that keep arriving together are served from the cache. Fresh cached responses
remain available while another format is serialized, even if that
serialization fails.
(#7994)
Fixed array- and map-valued attributes being serialized as the .NET type
name (e.g.
System.Byte[],System.Int32[]) instead of being JSON-encodedas per the specification.
byte[]-valued attributes are nowBase64-encoded, and other array- and map-valued attributes are now
JSON-encoded.
(#7694)
Fixed arrays of string-valued key/value pairs being
serialized as JSON arrays of strings instead of JSON objects.
(#7694)
Fixed scrape clients which stop reading their response delaying other
scrapes until
ScrapeResponseTimeoutMillisecondselapses.(#8041)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Fixed a scrape response containing the same series (metric name and labels)
more than once, which causes Prometheus to reject the whole response, such as
when metric or tag names are the same once escaped, tag names become the same
when UTF-8 encoded, or the scope information is disabled. Duplicate series are
now dropped, and a warning event is written.
A metric which has the name of a sample that is generated for another one
(for example
_sumof a histogram) is now dropped, and a warning event iswritten.
(#8076)
... (truncated)
Commits viewable in compare view.
Updated QRCoder from 1.8.0 to 1.8.1.
Release notes
Sourced from QRCoder's releases.
1.8.1
What's Changed
New Contributors
Full Changelog: Shane32/QRCoder@v1.8.0...v1.8.1
Commits viewable in compare view.
Updated WolverineFx from 6.51.2 to 6.64.0.
Release notes
Sourced from WolverineFx's releases.
6.64.0
A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.
Fixes
NativeAckendpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).IWolverineObserver.CircuitBreakerResetis now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened onCircuitBreakerTrippedcould never be closed by Wolverine's own signal. A new overload,CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own afterPauseTimeor through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).ResetResourceState()no longer adds a newwolverine.response.*queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, soInvokeAsync<T>()timed out (GH-5452, thanks to @alesdvorakcz).Docs
AutoCreate(#5445).What's Changed
ResetResourceState()calls by @alesdvorakcz in GH-5452: Rabbit MQ keeps one reply queue acrossResetResourceState()calls JasperFx/wolverine#5453Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0
6.63.0
This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (
src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.Fixes
Docs
CHAOS_*knobs and containers (GH-5409, GH-5414).What's Changed
... (truncated)
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
6.60.0
What's Changed
Full Changelog: JasperFx/wolverine@V6.59.1...V6.60.0
6.59.1
This is a patch release with two fixes. Upgrading is a package bump only: there is no schema change and no API change.
SQL Server: the inbox and outbox seek on their indexes again
sql_variant. The statements that mark envelopes as handled, reassign them, delete them and move them to the dead letter queue all filter on the envelope id. Weasel's generic command builder has no mapping forGuid, so it bound each id asDbType.Object, which SqlClient sends assql_variant. SQL Server then had to compareCONVERT_IMPLICIT(sql_variant, [id])on every row, which rules out a seek on theuniqueidentifierprimary key. Ids are now bound asuniqueidentifier, so each statement is a primary key seek.nvarchar.received_aton the inbox anddestinationon the outbox arevarchar(250)columns, but statements that filter on them bound the address asnvarchar. Under a SQL collation such asSQL_Latin1_General_CP1_CI_AS, the default on Azure SQL, that converts the column and defeats the index. The statements affected are the per-envelope updates and deletes, inbox recovery's page load, outbox loads by destination, the scheduled message updates and the duplicate check. They now bind the address asvarchar.DateTimeparameters kept only the date. The same generic mapping typedDateTimeasDbType.Date. The message store now lets SqlClient type both values itself.sql_variantand that no plan converts an indexed envelope column. The fullSqlServerTestssuite passes (721 tests, 2 skipped).Guidassql_variant) and JasperFx/weasel#759 (DateTimeasdate). Wolverine works around both on its own, so this release doesn't wait for a Weasel release.The
runcommand no longer blocks a thread pool threadruncommand waited for shutdown by blocking a thread pool thread for the whole life of the application. That matters when a container's CPU limit is below one core.ProcessorCountis then 1, so the thread pool's minimum is one thread, and theruncommand held it. After that, every burst of work had to wait for the pool to add a thread, about 500 ms each time. The reporter saw a 200 msTask.Delayloop wake up as much as about 950 ms late on Azure Container Apps.runcommand now awaits shutdown instead of blocking. It still listens for the same three signals:ApplicationStopping, Ctrl+C, and the assembly load context unloading.AutoStartHost/WebApplicationFactorypath),RunJasperFxCommands()used to block the calling thread. It now returns a task that completes when the host shuts down.RunJasperFxCommands()orRunWolverineCommands(), whatever its persistence or transport.Full Changelog: JasperFx/wolverine@V6.59.0...V6.59.1
6.59.0
New
ScheduledMessageSummary.SagaIdreports the saga id carried by each scheduled envelope. The newScheduledMessageQuery.SagaIdlimitsQueryAsyncandCancelAsyncto one saga's scheduled messages, such as its pending timeouts.PageSizeandTotalCountstay exact. On a large scheduled backlog, narrow the query withMessageTypeor an execution-time window as well.CancelAsyncwith aSagaIdthat matches nothing cancels nothing.PageSize <= 0as "read every match", as the RDBMS stores already did.WolverineFx.AI'sAddLlmCallouts()now works underTypeLoadMode.Staticwhen the application's pre-generated code was written without it. A library can ship its own static codegen and a host can add LLM callouts on top. In Static mode, callouts run on a pre-built handler that needs no generated code. Every other mode is unchanged.LlmCalloutOptions.ConfigureChain(Action<HandlerChain>)customizes the callout chain in any mode.IHandlerPolicydoesn't reach the pre-built handler.DeduplicateCalloutsis refused at startup in Static mode, because deduplication is woven into generated code.Fixes
IHost.StopAsync()cancels mid-flight is no longer logged as a send failure. Azure Service Bus hands the runtime's cancellation token to the SDK, so an orderly shutdown used to produce two Error lines for a batch that was never lost. A durable agent now logs it at Information, because the envelopes stay in the outbox and are recovered on restart. A non-durable agent logs it at Warning, because those messages were not sent. A shutdown cancellation no longer counts toward the circuit breaker or the sending failure policies. A cancellation while the application is still running, or any other exception during shutdown, is still logged at Error.6.58.0
New
GH-5279 (#5280, #5282): New opt-in
Durability.UseTransactionScopedDurabilityPassLockfor PostgreSQL. The serverless durability pass takes a transaction-scoped advisory lock (pg_try_advisory_xact_lock) instead of a session lock. This makes the pass lock safe behind a transaction-mode pooler such as PgBouncer or Supabase's pooler, where a session lock can leak onto a pooled connection or be held by two passes at once. #5282 hardens it:TransactionScopeidle_in_transaction_session_timeoutcan no longer drop the lock in the middle of a passWolverine also logs a one-time warning when the store doesn't support the setting, or when extension steps such as Marten's projection catch-up run under the open lock transaction. That open transaction can stall Marten's gap detection, which is tracked in JasperFx/marten#5791. See the serverless guide.
Fixes
ProcessingFailureinstead ofReceivedwhen its inbox could not store a batch. The sender keeps the batch and retries it, and a late duplicate is deduplicated by id. gRPC listeners can't be durable, so they aren't affected. A guard test now pins that.Durability.EnableInboxPartitioning, PostgreSQL's durable inbox now refuses a redelivery whose identity was already handled. Before, the kept Handled row sat in a different partition and didn't collide, so the redelivery was handled a second time. This completes the stable-id deduplication from 6.57.0 for partitioned inboxes.6.57.0
New
XmlSerializer, and they no longer have to switch to JSON before a migration to Wolverine can start. Every NServiceBus interop endpoint (Rabbit MQ, Azure Service Bus, Amazon SQS and SNS, and the SQL Server and PostgreSQL NServiceBus transports) now reads both JSON and XML, choosing per message from theNServiceBus.ContentTypeheader. To send XML, use the newNServiceBusXmlSerializer:.UseNServiceBusInterop().DefaultSerializer(new NServiceBusXmlSerializer()). Because one endpoint reads both formats, NServiceBus endpoints can also move from XML to JSON gradually. See XML Serialization with NServiceBus.Informationinstead of as an error.WolverineHttpOptions.RejectUnparseableHeaderValuesanswers 400 with ProblemDetails when a[FromHeader]value can't be parsed.Fixes
UseForReplies(). Wolverine used to give NServiceBus its ownwolverine.response.{guid}system queue as the reply address, which NServiceBus can't reach, so every reply ended up in NServiceBus's error queue.DurabilityAgent.StopAsync()now cancels its in-flight durability command and waits for it to finish. Before, a command still running at shutdown could outlive the host and fail against a disposed data source.WithDbContextAbstractionnow reuses the tenant DbContext, so repository writes, the save and outbox enrollment all use one context. This could previously fail code generation.[FromHeader]header binds the comma-joined values instead of answering 500.AndPauseProcessing()chained afterScheduleRetryIndefinitely()/RequeueIndefinitely()now apply, including to the open-ended attempts after the listed delays.Dependencies
Docs and build
./build.sh LocalGateruns every CI suite on one machine (GH-5125, #5246). The CI suites are rebalanced to stay under the 20 minute job limit (#5267), and the scaffold tests now pass on Windows (GH-5255, #5264).6.56.0
New
opts.UseHttpTransport()registers the HTTP transport insideUseWolverine().http/httpsURIs then resolve inListenForMessagesFrom(),PublishMessage<T>().To(uri), and runtimeEndpointFor()/ToDestination(). Before this, the transport was only registered byToHttpEndpoint(), and any otherhttpURI failed withUnknown Transport scheme 'http'./_wolverine/invokenow answers 415 instead of 500 for a content type with no registered serializer.Fixes
IHost.StopAsync()and throwObjectDisposedExceptionagainst a disposedNpgsqlDataSource.DeferAsync()used to call back into the receiver inline, so the failed inbox write and the defer recursed. A deferred Kafka envelope now goes back to the receiver on its own task after a short pause, and only while the listener is running. After a stop or inbox-recovery pause, its uncommitted offset brings it back. Because Kafka has no native requeue, aRequeueerror policy on a Kafka endpoint now redelivers after about one second instead of immediately./_wolverine/invokecould delete an outgoing envelope that was never received. HTTP transport responses are now disposed.6.55.1
Fixes
DatabaseBatchCommandExceptionand logged as an Error. Genuine SQL/connection failures are still reported.HttpEndpointaimed at/_wolverine/invokein its default (buffered) mode now delivers by posting each envelope individually, instead of receiving a 415 for every batch and retrying forever./batch/{queue}and.SendInline()endpoints are unchanged.6.55.0
Highlights
WolverineFx.Bobcat is out of alpha, on Bobcat 1.0.0 (#5222, #5229). Bobcat 1.0.0 shipped tonight, and
WolverineFx.BobcatandWolverineFx.Bobcat.EventModelnow publish as stable 6.55.0 instead of-alpha.1.WolverineFx.Bobcat.Httpstays6.55.0-alpha.1until Alba 9 ships stable, because a stable package cannot depend on Alba 9.0.0-rc.2. A spec project thatwrite-specsgenerates with no--wolverine-versionpins the stableWolverineFx.Bobcat(#5222, #5223).MessageCausedBynames your handler (#5224, #5225).IWolverineObserver.MessageCausedByreported the generated handler class (Internal.Generated.WolverineHandlers.StartTripHandler939323516). It now reports the handler you wrote (TripService.StartTripHandler), the same string as themessage.handlerspan tag, resolved at codegen time. Code generated by an earlier version keeps working through the old overload.CosmosDB sagas start with a conditional create (#5221, thanks @thechucklingatom). A second start message for an existing saga id used to silently overwrite the running saga. It now fails with the
SagaConcurrencyExceptionthat Marten, Azure Blob and S3 already raise, so oneOnException<SagaConcurrencyException>()policy covers every provider.Fixes
ListeningAgent.StartAsyncis serialized, and deliveries are deferred to a drainedBufferedReceiver(#5228)CancellationTokenSource(#5226)Dependencies
Originno longer raises aSourceDisagreement)Full Changelog: JasperFx/wolverine@V6.54.0...V6.55.0
6.54.0
Highlights
Dead letter failure groups (#5209, #5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:
IDeadLetterFingerprinterhashes the exception type and the first stack frame from application code. Register your own to replace it.DeadLetterEnvelopeQuerygainsFailureGroup,ExceptionMessageMatch(Exact / Contains),TenantIdandArchived.SummarizeAllAsyncoverload groups by failure group, message type or endpoint, with first and last failure times.ReplayMatchingAsync,DiscardMatchingAsync,ArchiveMatchingAsyncandRestoreMatchingAsyncreport how many dead letters they affected.ReplayCount,LastReplayedAtandFirstFailedAt.DurabilitySettings.ArchivedDeadLetterRetention.IDeadLetters.Capabilitiestells you what a store supports.All changes are additive. The relational stores pick up seven nullable columns on
wolverine_dead_letters, an index and a newwolverine_dead_letter_historytable through the normal schema migration. See the dead letter storage guide.Deduplication fixes (#5205, #5206, #5208), and Bobcat 1.0.0-rc.4 dependency pins (#5211). The
WolverineFx.Bobcat*packages remain alpha (6.54.0-alpha.1).What's Changed
Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0
6.53.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0
6.52.0
Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with
UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.Many thanks to everyone who reported issues and sent fixes: @uniquelau, @johnkaram02, @erdtsieck, @ahmetvayhan and @pritamrao.
Aspire parity: named connections
NpgsqlDataSource/MySqlDataSourcefrom the container, named static tenants, a Named Connection Strings table indescribe, and docs that lead with the named form (GH-5127, GH-5156) by @jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174wolverine.slnx, with a ServiceDefaults project for traces, metrics and/health(GH-5124) by @jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182Messaging and error handling
opts.Schedules.TimerThreshold(15 minutes), same dedup id as the scheduled path, pause and resume throughIRecurringScheduleControl(GH-5168) by @jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183DoThenRetry(action, maxAttempts)error policy that works both inline and from a queue (GH-5068) by @jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandleris[Obsolete](still the default), a startup warning for combined handlers, opt-inAssertNoCombinedHandlers(), fixes for latentSeparatedbugs, ahandler.typeOpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184HTTP
[DeduplicatedWithResponse]ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @jeremydmiller with @uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173Content-Length(GH-5187) by @johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188[FromQuery]name is not a C# identifier (GH-5189) by @johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190Operability and diagnostics
ServiceCapabilitiesreads each store on its own and reportsFailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175AssignmentGrid.Agent.UnplacedReason(AwaitingCapacity,NoCapableNode,Paused,TakeoverHold,Superseded), a capacity log line and an optionalNodeAcceptThreshold(GH-5163) by @jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181db-list/db-dump/db-patchdiscover the Oracle message store (GH-5172) by @jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177Documentation
_...
Description has been truncated