Bump the nuget-minor-patch group with 13 updates#96
Closed
dependabot[bot] wants to merge 2 commits into
Closed
Conversation
Bumps AndreGoepel.Design.Blazor from 1.0.2 to 1.0.3 Bumps AndreGoepel.Marten.Identity.Blazor from 1.3.1 to 1.3.3 Bumps Microsoft.AspNetCore.HeaderPropagation from 10.0.9 to 10.0.10 Bumps Microsoft.Extensions.Http.Resilience from 10.7.0 to 10.8.0 Bumps Microsoft.Extensions.ServiceDiscovery from 10.7.0 to 10.8.0 Bumps Microsoft.NET.Test.Sdk from 18.7.0 to 18.8.1 Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.16.0 to 1.17.0 Bumps OpenTelemetry.Extensions.Hosting from 1.16.0 to 1.17.0 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.16.0 to 1.17.0 Bumps OpenTelemetry.Instrumentation.Http from 1.16.0 to 1.17.0 Bumps OpenTelemetry.Instrumentation.Runtime from 1.16.0 to 1.17.0 Bumps WolverineFx.Marten from 6.17.1 to 6.20.0 Bumps WolverineFx.RuntimeCompilation from 6.17.1 to 6.20.0 --- updated-dependencies: - dependency-name: AndreGoepel.Design.Blazor dependency-version: 1.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: AndreGoepel.Marten.Identity.Blazor dependency-version: 1.3.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: Microsoft.AspNetCore.HeaderPropagation dependency-version: 10.0.10 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.8.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Microsoft.Extensions.ServiceDiscovery dependency-version: 10.8.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.8.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: OpenTelemetry.Instrumentation.Http dependency-version: 1.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: OpenTelemetry.Instrumentation.Runtime dependency-version: 1.17.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: WolverineFx.Marten dependency-version: 6.20.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.20.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
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 AndreGoepel.Design.Blazor from 1.0.2 to 1.0.3.
Release notes
Sourced from AndreGoepel.Design.Blazor's releases.
1.0.3
What's Changed
Full Changelog: andregoepel/design-blazor@v1.0.2...v1.0.3
Commits viewable in compare view.
Updated AndreGoepel.Marten.Identity.Blazor from 1.3.1 to 1.3.3.
Release notes
Sourced from AndreGoepel.Marten.Identity.Blazor's releases.
1.3.3
What's Changed
Full Changelog: andregoepel/marten-identity@v1.3.2...v1.3.3
1.3.2
What's Changed
Full Changelog: andregoepel/marten-identity@v1.3.1...v1.3.2
Commits viewable in compare view.
Updated Microsoft.AspNetCore.HeaderPropagation from 10.0.9 to 10.0.10.
Release notes
Sourced from Microsoft.AspNetCore.HeaderPropagation's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.Extensions.Http.Resilience from 10.7.0 to 10.8.0.
Release notes
Sourced from Microsoft.Extensions.Http.Resilience's releases.
10.8.0
This release adds new experimental APIs to Microsoft.Extensions.AI.Abstractions and updates the OpenAI dependency to 2.12.0, alongside documentation, test, and repository maintenance.
Experimental API Changes
New Experimental APIs
AIFunctionNameAttributeandAIParameterNameAttribute#7610 by @jozkee (co-authored by @jeffhandley @Copilot)ToolApprovalRequestContent.RequiresConfirmation(MEAI001) #7549 by @javiercn (co-authored by @Copilot)What's Changed
AI
Vector Data
Documentation Updates
Test Improvements
Repository Infrastructure Updates
... (truncated)
Commits viewable in compare view.
Updated Microsoft.Extensions.ServiceDiscovery from 10.7.0 to 10.8.0.
Release notes
Sourced from Microsoft.Extensions.ServiceDiscovery's releases.
10.8.0
This release adds new experimental APIs to Microsoft.Extensions.AI.Abstractions and updates the OpenAI dependency to 2.12.0, alongside documentation, test, and repository maintenance.
Experimental API Changes
New Experimental APIs
AIFunctionNameAttributeandAIParameterNameAttribute#7610 by @jozkee (co-authored by @jeffhandley @Copilot)ToolApprovalRequestContent.RequiresConfirmation(MEAI001) #7549 by @javiercn (co-authored by @Copilot)What's Changed
AI
Vector Data
Documentation Updates
Test Improvements
Repository Infrastructure Updates
... (truncated)
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.7.0 to 18.8.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.8.1
What's Changed
Full Changelog: microsoft/vstest@v18.8.0...v18.8.1
18.8.0
What's Changed
Full Changelog: microsoft/vstest@v18.7.0...v18.8.0
Commits viewable in compare view.
Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.16.0 to 1.17.0.
Release notes
Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.
1.17.0
For highlights and announcements pertaining to this release see: Release Notes > 1.17.0.
The following changes are from the previous release 1.17.0-rc.1.
NuGet: OpenTelemetry v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Zipkin v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Extensions.Hosting v1.17.0
No notable changes.
... (truncated)
1.17.0-rc.1
The following changes are from the previous release 1.16.0.
NuGet: OpenTelemetry v1.17.0-rc.1
Fixed a metric point reclaim data race on CPU ARM architectures.
(#7401)
The library is now marked as trim and AOT compatible.
(#7441)
Replaced the vendored copy of
EnvironmentVariablesConfigurationProviderwith a directMicrosoft.Extensions.Configuration.EnvironmentVariablespackage dependency.Consumers gain automatic pickup of upstream bug fixes and security patches;
no public API or behavioural change.
(#7146)
Added a verbose
OpenTelemetry-Sdkself-diagnostics event that is emittedwhen an activity is dropped because its local (in-process) parent is not
recorded.
(#7427)
Added support for a Schema URL on
Resourceinstances.(#7472)
Fixed a metric storage leak that occurred when meters and instruments were
repeatedly created and disposed.
(#7466)
Added
ExcludedTagKeysproperty toMetricStreamConfigurationto supportexcluding specific tag keys from metric streams.
(#7373)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.17.0-rc.1
Fixed
TraceContextPropagatorto normalize emptytracestateheader valuesto
nullwhen extracting trace context.(#7407,
#7433)
The library is now marked as trim and AOT compatible.
(#7441)
Experimental (pre-release builds only): Updated
EnvironmentVariableCarrier.Getto read only the normalized environment variable name, following the updated
environment variable carrier specification.
Non-normalized carrier keys are no longer matched, even when they would
normalize to the requested key.
... (truncated)
1.17.0-beta.1
The following changes are from the previous release 1.16.0-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.17.0-beta.1
Added a verbose-level diagnostic event for ignored metrics.
(#7429)
The library is now marked as trim and AOT compatible.
(#7441)
Fix double unit suffixes in metric names when using OpenMetrics.
(#7454)
Fix incorrect handling of leading digits in metric names for OpenMetrics.
(#7454)
Add
PrometheusAspNetCoreOptions.ScopeInfoEnabledproperty to enable ordisable scope labels in Prometheus metrics. Defaults to
true.(#7436)
Added support for the
dotsandvaluesPrometheus UTF-8 name escapingschemes when negotiated via the
Acceptheader.(#7439)
Add
PrometheusAspNetCoreOptions.TargetInfoEnabledproperty to enable ordisable the
target_infometric in Prometheus metrics. Defaults totrue.(#7438)
Added support for the
allow-utf-8Prometheus UTF-8 name escaping schemewhen negotiated via the
Acceptheader.(#7440)
Add
PrometheusAspNetCoreOptions.ResourceConstantLabelsproperty to selectresource attributes to add to each metric as constant labels. Defaults to
null(no resource attributes are added as metric labels).(#7471)
Add
PrometheusAspNetCoreOptions.MaxScrapeResponseSizeBytesto configurethe maximum size of a scrape response. The default is now ~166 MiB.
(#7487)
A scrape whose serialized output exceeds the maximum scrape response size
limit now responds with HTTP 500.
(#7487)
Fixed the Prometheus text exposition format emitting redundant comments.
(#7491)
Made
Acceptheader content negotiation consistent with thePrometheusHttpListenerendpoint.... (truncated)
Commits viewable in compare view.
Updated OpenTelemetry.Extensions.Hosting from 1.16.0 to 1.17.0.
Release notes
Sourced from OpenTelemetry.Extensions.Hosting's releases.
1.17.0
For highlights and announcements pertaining to this release see: Release Notes > 1.17.0.
The following changes are from the previous release 1.17.0-rc.1.
NuGet: OpenTelemetry v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Zipkin v1.17.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Extensions.Hosting v1.17.0
No notable changes.
... (truncated)
1.17.0-rc.1
The following changes are from the previous release 1.16.0.
NuGet: OpenTelemetry v1.17.0-rc.1
Fixed a metric point reclaim data race on CPU ARM architectures.
(#7401)
The library is now marked as trim and AOT compatible.
(#7441)
Replaced the vendored copy of
EnvironmentVariablesConfigurationProviderwith a directMicrosoft.Extensions.Configuration.EnvironmentVariablespackage dependency.Consumers gain automatic pickup of upstream bug fixes and security patches;
no public API or behavioural change.
(#7146)
Added a verbose
OpenTelemetry-Sdkself-diagnostics event that is emittedwhen an activity is dropped because its local (in-process) parent is not
recorded.
(#7427)
Added support for a Schema URL on
Resourceinstances.(#7472)
Fixed a metric storage leak that occurred when meters and instruments were
repeatedly created and disposed.
(#7466)
Added
ExcludedTagKeysproperty toMetricStreamConfigurationto supportexcluding specific tag keys from metric streams.
(#7373)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.17.0-rc.1
Fixed
TraceContextPropagatorto normalize emptytracestateheader valuesto
nullwhen extracting trace context.(#7407,
#7433)
The library is now marked as trim and AOT compatible.
(#7441)
Experimental (pre-release builds only): Updated
EnvironmentVariableCarrier.Getto read only the normalized environment variable name, following the updated
environment variable carrier specification.
Non-normalized carrier keys are no longer matched, even when they would
normalize to the requested key.
... (truncated)
1.17.0-beta.1
The following changes are from the previous release 1.16.0-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.17.0-beta.1
Added a verbose-level diagnostic event for ignored metrics.
(#7429)
The library is now marked as trim and AOT compatible.
(#7441)
Fix double unit suffixes in metric names when using OpenMetrics.
(#7454)
Fix incorrect handling of leading digits in metric names for OpenMetrics.
(#7454)
Add
PrometheusAspNetCoreOptions.ScopeInfoEnabledproperty to enable ordisable scope labels in Prometheus metrics. Defaults to
true.(#7436)
Added support for the
dotsandvaluesPrometheus UTF-8 name escapingschemes when negotiated via the
Acceptheader.(#7439)
Add
PrometheusAspNetCoreOptions.TargetInfoEnabledproperty to enable ordisable the
target_infometric in Prometheus metrics. Defaults totrue.(#7438)
Added support for the
allow-utf-8Prometheus UTF-8 name escaping schemewhen negotiated via the
Acceptheader.(#7440)
Add
PrometheusAspNetCoreOptions.ResourceConstantLabelsproperty to selectresource attributes to add to each metric as constant labels. Defaults to
null(no resource attributes are added as metric labels).(#7471)
Add
PrometheusAspNetCoreOptions.MaxScrapeResponseSizeBytesto configurethe maximum size of a scrape response. The default is now ~166 MiB.
(#7487)
A scrape whose serialized output exceeds the maximum scrape response size
limit now responds with HTTP 500.
(#7487)
Fixed the Prometheus text exposition format emitting redundant comments.
(#7491)
Made
Acceptheader content negotiation consistent with thePrometheusHttpListenerendpoint.... (truncated)
Commits viewable in compare view.
Updated OpenTelemetry.Instrumentation.AspNetCore from 1.16.0 to 1.17.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.
1.17.0
NuGet: OpenTelemetry.Exporter.Geneva v1.17.0
Updated OpenTelemetry core component version(s) to
1.17.0.(#4773)
Updated ETW manifest and payload in
EtwDataTransportwith synthetic payload so that the runtime-generated .NET
ETW manifest matches the actual payload.
(#4729
See CHANGELOG for details.
1.17.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.17.0-rc.1
1.17.0.(#4773)
See CHANGELOG for details.
1.17.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.17.0-beta.1
1.17.0.(#4773)
See CHANGELOG for details.
1.17.0-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.17.0-alpha.1
Assemblies are now digitally signed using cosign.
(#4637)
Updated OpenTelemetry core component version(s) to
1.17.0.(#4773)
See CHANGELOG for details.
Commits viewable in compare view.
Updated OpenTelemetry.Instrumentation.Http from 1.16.0 to 1.17.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.Http's releases.
1.17.0
NuGet: OpenTelemetry.Exporter.Geneva v1.17.0
Updated OpenTelemetry core component version(s) to
1.17.0.(#4773)
Updated ETW manifest and payload in
EtwDataTransportwith synthetic payload so that the runtime-generated .NET
ETW manifest matches the actual payload.
(#4729
See CHANGELOG for details.
1.17.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.17.0-rc.1
1.17.0.(#4773)
See CHANGELOG for details.
1.17.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.17.0-beta.1
1.17.0.(#4773)
See CHANGELOG for details.
1.17.0-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.17.0-alpha.1
Assemblies are now digitally signed using cosign.
(#4637)
Updated OpenTelemetry core component version(s) to
1.17.0.(#4773)
See CHANGELOG for details.
Commits viewable in compare view.
Updated OpenTelemetry.Instrumentation.Runtime from 1.16.0 to 1.17.0.
Release notes
Sourced from OpenTelemetry.Instrumentation.Runtime's releases.
1.17.0
NuGet: OpenTelemetry.Exporter.Geneva v1.17.0
Updated OpenTelemetry core component version(s) to
1.17.0.(#4773)
Updated ETW manifest and payload in
EtwDataTransportwith synthetic payload so that the runtime-generated .NET
ETW manifest matches the actual payload.
(#4729
See CHANGELOG for details.
1.17.0-rc.1
NuGet: OpenTelemetry.Instrumentation.Process v1.17.0-rc.1
1.17.0.(#4773)
See CHANGELOG for details.
1.17.0-beta.1
NuGet: OpenTelemetry.Extensions.Enrichment v1.17.0-beta.1
1.17.0.(#4773)
See CHANGELOG for details.
1.17.0-alpha.1
NuGet: OpenTelemetry.Instrumentation.EventCounters v1.17.0-alpha.1
Assemblies are now digitally signed using cosign.
(#4637)
Updated OpenTelemetry core component version(s) to
1.17.0.(#4773)
See CHANGELOG for details.
Commits viewable in compare view.
Updated WolverineFx.Marten from 6.17.1 to 6.20.0.
Release notes
Sourced from WolverineFx.Marten's releases.
6.20.0
Wolverine 6.20.0
Dependency upgrades (critter stack)
Multi-tenancy & connection footprint
nodes × databases. Plus daemon tracker-subscription leak hygiene.IntegrateWithWolverine()now honors a database-per-tenant Polecat store and readsMainDatabaseConnectionString.DatabaseDescriptor.Portinstead of re-parsing (jasperfx#514).CritterWatch / connection state
Kafka
SentAtand expose record headers on raw-JSON listeners (GH-3407).JsonSerializerOptionson raw-JSON endpoints now actually applies;PublishRawJsonmapper registration fixed.Sagas
SagaConcurrencyExceptionnow inheritsJasperFx.ConcurrencyException(GH-3444) — existingOnException<ConcurrencyException>()policies now catch saga concurrency failures.Other
TrackedSessionnot-tracked vs not-routed fix (#3435).6.19.0
CosmosDB
CosmosDbConfiguration.PartitionSagasById(): opt-in, saga id becomes the document partition key (GH-3415) @mysticmindCosmosClientwhose serializer would drop a saga'sidat host start; document the camelCase requirement (GH-3416) @mysticmindHTTP / OpenAPI
uuidinstead of falling back tostring(GH-3420) @mysticmindDurability / persistence
IWolverineObserver.ConnectionBudget(GH-3397) @jeremydmillerTest infrastructure only
IntegrationContextfrom disposing a class fixture it doesn't own; pinApplicationAssemblyin the CoreTests harness (GH-3423) @jeremydmillerusing_dynamic_multi_tenancyfrom poisoning its own next run @mysticmindMilestone: https://github.com/JasperFx/wolverine/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3A6.19.0
Full Changelog: JasperFx/wolverine@V6.18.0...V6.19.0
6.18.0
Wolverine 6.18.0
A security-relevant serialization fix, a startup-fatal codegen fix, a silently-dead-listener fix in RabbitMQ, the first F# saga codegen support of any persistence provider, and the CI split that makes "merge when green" mean something again.
If you use MassTransit interop over a durable listener, take this release. See the first section.
#3408 — fixed in #3411
EnvelopeSerializerwrote the typed envelope properties to the wire format and then appended everyEnvelope.Headersentry verbatim, with no reserved-key filter — and the appended entries came last. Because the reader parses reserved keys straight back into typed properties, aHeadersentry under a reserved key silently overwrote the real property on the next read.A value in
envelope.Headers["tenant-id"]is inert while the envelope is in memory. It stops being inert the moment the envelope crosses the serializer — any durable listener, the inbox/outbox, or the scheduled-message store:tenant-idintoenvelope.Headers.env.TenantIdis set from it.saga-idreaches another saga's state, andidrewritesEnvelope.Id— the inbox's dedupe identity.This was live, not theoretical.
MassTransitEnvelope.TransferDataalready copies every incoming MassTransit header intoenvelope.Headersunfiltered (and by assignment, notTryAdd). Any Wolverine app doing MassTransit interop over a durable listener has had this path open. If that describes you, this release is the one to take.The fix filters reserved keys on the write side, so the typed property stays authoritative and a reserved key sitting in
Headersbecomes a no-op.causation-idis deliberately not filtered —DeliveryOptionsintentionally carries it as a loose header forWolverine.Marten'sOutboxedSessionFactory, and it is never promoted by the reader.Startup-fatal codegen fix
#3399 — fixed in #3406 — invalid generated class name for batched (array) message types. This one prevents the application from starting.
Fixes
DaemonMode.Solo/HotColddaemon alongside managed distribution is now an actionable startup exception instead of two schedulers quietly fighting over the same shards.IAgentRuntime.ApplyRestrictionsAsyncpersisted the restriction and then never dispatched the commands it computed, so pausing an agent had no immediate effect. Reported by @erdtsieck against a live cluster.Internalstatus. It now returns an actionable diagnostic telling you to put the saga identity on the request DTO.[AsParameters]now rejects unparseable values in collection query parameters, closing the gap left by the scalar fix in #3372.IEventStorebridge registered twice, soGetServices<IEventStore>()returned the same store instance two times and anything iterating it double-counted. Polecat's ownAddPolecat()had started registeringIEventStoreand Wolverine was still bridging it as well.State = Connected— a silently dead listener. The listener now defers toReconnectedAsync(), which re-declares and re-consumes. Also pins theConnectionMonitortracking invariant that #3370 fixed but nothing guarded.OpenAPI
#3380 (#3418) — OpenAPI parameters are now derived from the full binding chain rather than the handler signature alone. Two real defects closed:
After/Finallypostprocessor were omitted from the operation entirely.string) whenever the description was assembled before those frames resolved — which is exactly the build-time OpenAPI /openapiCLI path, because ASP.NET caches the first ApiExplorer read.More importantly, this ships the OpenAPI shape-test harness that was missing. Adding a shape assertion is now one endpoint plus one
[Fact], which is why this class of omission kept shipping unnoticed.New: Azure Service Bus emulator support
#3366 (#3409) — the docs told you to call
UseAzureServiceBusTesting(), which only ever existed in Wolverine's own test suite. It is now a real, shipping API:... (truncated)
6.17.3
Bug-fix and scale release, following the 6.17.2 community sweep. Every item below came from a community report or a review finding — thank you all.
Closed issues
PeriodicTimer, so at high database counts the metrics polling itself became significant connection pressure. Agents now register their store with a node-wide sequential sweeper that walks the node's databases one at a time across theUpdateMetricsPeriodwindow — at most one metrics connection in flight per node, regardless of database count. The registration set is re-read every pass, so databases join and leave the sweep as agents start and stop without a restart.Disconnectedstate that #3187 fixed. Two follow-ups are tracked in #3391.TrackedSessionwould pick up and then sit waiting on messages the test never sent. The default ignore rule now covers all ofINotToBeRouted(agent commands and framework telemetry), with a deliberate carve-out forAcknowledgement/FailureAcknowledgement, which the session's own acknowledgement APIs depend on. If you are on an older version,IgnoreMessagesMatchingType(t => t.CanBeCastTo<INotToBeRouted>())is the workaround.Fixes from review
UpdateMetricsPeriod = TimeSpan.Zerowould hot-spin the sweep loop (the pre-#3384PeriodicTimerthrew); it is now rejected at configuration time, withDurabilityMetricsEnabled = falseas the way to turn polling off.Marten test-helper:
PauseThenCatchUpOnMartenDaemonActivity#3388 — cold first catch-up appeared to stall (PR #3394, reported by @uniquelau). Investigated in depth. The reported mechanism — that
coordinator.ResumeAsync()does not start never-started shards — does not hold: under Wolverine-managed distribution the coordinator isWolverineProjectionCoordinator, whoseResumeAsyncbuilds the daemon lazily and starts every shard, bypassing agent assignment entirely. The cold path works, and there are now four tests proving it (including with a second subscription-agent consumer sharing the agent family).The real defect was a timeout mismatch, and it explains the reported symptom exactly. The stage runs inside a child
TrackedSessionwhose token cancels atTrackedSession.Timeout— 5 seconds by default — while the catch-up ignored that token and waited on an internal 60-second budget. The session gave up first and left the catch-up envelope started-but-never-finished, which reads as a hang. This is a genuine 6.16 → 6.17 behavior change: the old activeForceAllfinished inside 5 seconds; resume-and-wait on a cold daemon or a busy machine does not. The catch-up now honors the session's token and raises an actionableTimeoutExceptionnaming the store and pointing atTrackActivity().Timeout(...).If you hit this on 6.17.0–6.17.2, raising the tracked-session timeout is the fix.
Docs
IMessageBus.InvokeAsync<T>and the chain that runs is the handler's. The header-identified gap is tracked as #3385, with a clear diagnostic planned.Timeout()bounds the whole session including its stages, so a slow stage likePauseThenCatchUpOnMartenDaemonActivity()is capped by the session's 5-second default, not by any budget internal to the stage.Full changelog: JasperFx/wolverine@V6.17.2...V6.17.3
6.17.2
Community-issue sweep release. Every fix below shipped same-day from issues filed by the community — thank you all.
Closed issues
WolverineApiDescriptionProvidernow enumerates theHttpGraph(complete whenMapWolverineEndpoints()returns) instead of the start-timeEndpointDataSource, so ASP.NET's version-keyed cache can never freeze an empty first read. If you monitor Wolverine hosts with CritterWatch and expose OpenAPI, upgrade to this release (see JasperFx/CritterWatch#689).[AsParameters]+ compound-handlerLoadAsyncbinding the same route variable generated uncompilable code (CS0136/CS0841, host failed at startup) (PR #3381). Binding frames are now emitted once per chain and re-homed so any second consumer reuses them; both the[FromRoute]and[AsParameters]-parameter variants are covered. The related OpenAPI gap (route params bound only byLoadAsyncmissing from the operation) is tracked as #3380.[AsParameters]query binder silently ignored unparseable values (PR #3379). New opt-inWolverineHttpOptions.RejectUnparseableQueryValues: a present-but-unparseable query value short-circuits with a 400 ProblemDetails naming the parameter, matching ASP.NET minimal APIs; missing values keep their initializer in both modes. The default flips to strict in Wolverine 7.0.IMessageContext, plus a fullITenantDetectionPolicies-style mirror (opts.TenantId.IsRequestHeaderValue(...),IsClaimTypeNamed(...),DetectWith<T>()) that sets the codegen tenant variable Marten/Polecat session frames consume — with a zero-config default when the client stampstenant-id. New docs page: gRPC multi-tenancy.DurabilityMetricsEnabled = falseand raisingUpdateMetricsPeriodas mitigations for metrics-polling connection load at high tenant-database counts (PR #3378). The per-node sweeper implementation is in progress on the issue.Dependency bumps
Commits viewable in compare view.
Updated WolverineFx.RuntimeCompilation from 6.17.1 to 6.20.0.
Release notes
Sourced from WolverineFx.RuntimeCompilation's releases.
6.20.0
Wolverine 6.20.0
Dependency upgrades (critter stack)
Multi-tenancy & connection footprint
nodes × databases. Plus daemon tracker-subscription leak hygiene.IntegrateWithWolverine()now honors a database-per-tenant Polecat store and readsMainDatabaseConnectionString.DatabaseDescriptor.Portinstead of re-parsing (jasperfx#514).CritterWatch / connection state
Kafka
SentAtand expose record headers on raw-JSON listeners (GH-3407).JsonSerializerOptionson raw-JSON endpoints now actually applies;PublishRawJsonmapper registration fixed.Sagas
SagaConcurrencyExceptionnow inheritsJasperFx.ConcurrencyException(GH-3444) — existingOnException<ConcurrencyException>()policies now catch saga concurrency failures.Other
TrackedSessionnot-tracked vs not-routed fix (#3435).6.19.0
CosmosDB
CosmosDbConfiguration.PartitionSagasById(): opt-in, saga id becomes the document partition key (GH-3415) @mysticmindCosmosClientwhose serializer would drop a saga'sidat host start; document the camelCase requirement (GH-3416) @mysticmindHTTP / OpenAPI
uuidinstead of falling back tostring(GH-3420) @mysticmindDurability / persistence
IWolverineObserver.ConnectionBudget(GH-3397) @jeremydmillerTest infrastructure only
IntegrationContextfrom disposing a class fixture it doesn't own; pinApplicationAssemblyin the CoreTests harness (GH-3423) @jeremydmillerusing_dynamic_multi_tenancyfrom poisoning its own next run @mysticmindMilestone: https://github.com/JasperFx/wolverine/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3A6.19.0
Full Changelog: JasperFx/wolverine@V6.18.0...V6.19.0
6.18.0
Wolverine 6.18.0
A security-relevant serialization fix, a startup-fatal codegen fix, a silently-dead-listener fix in RabbitMQ, the first F# saga codegen support of any persistence provider, and the CI split that makes "merge when green" mean something again.
If you use MassTransit interop over a durable listener, take this release. See the first section.
#3408 — fixed in #3411
EnvelopeSerializerwrote the typed envelope properties to the wire format and then appended everyEnvelope.Headersentry verbatim, with no reserved-key filter — and the appended entries came last. Because the reader parses reserved keys straight back into typed properties, aHeadersentry under a reserved key silently overwrote the real property on the next read.A value in
envelope.Headers["tenant-id"]is inert while the envelope is in memory. It stops being inert the moment the envelope crosses the serializer — any durable listener, the inbox/outbox, or the scheduled-message store:tenant-idintoenvelope.Headers.env.TenantIdis set from it.saga-idreaches another saga's state, andidrewritesEnvelope.Id— the inbox's dedupe identity.This was live, not theoretical.
MassTransitEnvelope.TransferDataalready copies every incoming MassTransit header intoenvelope.Headersunfiltered (and by assignment, notTryAdd). Any Wolverine app doing MassTransit interop over a durable listener has had this path open. If that describes you, this release is the one to take.The fix filters reserved keys on the write side, so the typed property stays authoritative and a reserved key sitting in
Headersbecomes a no-op.causation-idis deliberately not filtered —DeliveryOptionsintentionally carries it as a loose header forWolverine.Marten'sOutboxedSessionFactory, and it is never promoted by the reader.Startup-fatal codegen fix
#3399 — fixed in #3406 — invalid generated class name for batched (array) message types. This one prevents the application from starting.
Fixes
DaemonMode.Solo/HotColddaemon alongside managed distribution is now an actionable startup exception instead of two schedulers quietly fighting over the same shards.IAgentRuntime.ApplyRestrictionsAsyncpersisted the restriction and then never dispatched the commands it computed, so pausing an agent had no immediate effect. Reported by @erdtsieck against a live cluster.Internalstatus. It now returns an actionable diagnostic telling you to put the saga identity on the request DTO.[AsParameters]now rejects unparseable values in collection query parameters, closing the gap left by the scalar fix in #3372.IEventStorebridge registered twice, soGetServices<IEventStore>()returned the same store instance two times and anything iterating it double-counted. Polecat's ownAddPolecat()had started registeringIEventStoreand Wolverine was still bridging it as well.State = Connected— a silently dead listener. The listener now defers toReconnectedAsync(), which re-declares and re-consumes. Also pins theConnectionMonitortracking invariant that #3370 fixed but nothing guarded.OpenAPI
#3380 (#3418) — OpenAPI parameters are now derived from the full binding chain rather than the handler signature alone. Two real defects closed:
After/Finallypostprocessor were omitted fro...Description has been truncated