chore(deps): Bump the minor-and-patch group with 9 updates#89
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
chore(deps): Bump the minor-and-patch group with 9 updates#89dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps Anthropic from 12.16.0 to 12.20.0 Bumps Aspire.Npgsql from 13.2.3 to 13.2.4 Bumps Marten from 8.32.1 to 8.36.0 Bumps Marten.EntityFrameworkCore from 8.32.1 to 8.36.0 Bumps SonarAnalyzer.CSharp from 10.24.0.138807 to 10.25.0.139117 Bumps WolverineFx from 5.32.1 to 5.37.2 Bumps WolverineFx.EntityFrameworkCore from 5.32.1 to 5.37.2 Bumps WolverineFx.Marten from 5.32.1 to 5.37.2 Bumps YamlDotNet from 17.0.1 to 17.1.0 --- updated-dependencies: - dependency-name: Anthropic dependency-version: 12.20.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Aspire.Npgsql dependency-version: 13.2.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch - dependency-name: Marten dependency-version: 8.36.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: Marten.EntityFrameworkCore dependency-version: 8.36.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: SonarAnalyzer.CSharp dependency-version: 10.25.0.139117 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx dependency-version: 5.37.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 5.37.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: WolverineFx.Marten dependency-version: 5.37.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch - dependency-name: YamlDotNet dependency-version: 17.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
Dependency ReviewThe following issues were found:
License Issuesbackend/src/RunCoach.Api/RunCoach.Api.csproj
backend/tests/RunCoach.Api.Tests/RunCoach.Api.Tests.csproj
OpenSSF ScorecardScorecard details
Scanned Files
|
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 Anthropic from 12.16.0 to 12.20.0.
Updated Aspire.Npgsql from 13.2.3 to 13.2.4.
Release notes
Sourced from Aspire.Npgsql's releases.
13.2.4
Aspire 13.2.4
What's New in Aspire 13.2.4
Patch release addressing a security advisory in OpenTelemetry dependencies.
🐛 Fixes
🏷️ Housekeeping
13.2.4 (#16436)
Commits viewable in compare view.
Updated Marten from 8.32.1 to 8.36.0.
Release notes
Sourced from Marten's releases.
8.36.0
Highlights
Marten 8.36.0 closes out #4329 by adopting JasperFx.Events 1.35.0 and ships the corresponding docs and integration tests, plus a separately-tracked docs improvement for modular
IConfigureMartenprojection registration (#4326) and two LINQ fixes.Options.CacheLimitPerTenantis a memory tunable again, not a correctness lever for downstreamEnrichWith<T>/TryFindUpstreamCachelookups.ForEntityIdsfor fan-out enrichment (via JasperFx.Events 1.35.0). New first-class declarative shape for events that reference several entities of the same type:composite.mdcalls out that downstream stages can't SQL-query upstream stages' in-flight writes, lists the four supported alternatives (Updated<T>synthetic events,EnrichWith<T>().AddReferences(),TryFindUpstreamCache<TId, T>,ReferencePeerView<T>), and includes inline samples sourced from the integration tests.IConfigureMarten+ DI projection registration docs. New section inevents/projections/ioc.mdshowing how a module-style configuration can register a service-aware projection by taking its dependencies through theIConfigureMartenconstructor and building the projection insideConfigure(...). Closes #4326.string[].Containsparse failure under C# 14 + nullable + method init (#4332), andWhereclauses on the inner source ofGroupJoinare now honored.What's Changed
Whereclauses on the inner source ofGroupJoinby @snrnats in HonorWhereclauses on the inner source ofGroupJoinJasperFx/marten#4331New Contributors
Whereclauses on the inner source ofGroupJoinJasperFx/marten#4331Full Changelog: JasperFx/marten@V8.35.0...V8.36.0
8.35.0
Heads up, this will cause a DDL change for some upsert functions due to a bug that was only apparent under high concurrency
What's Changed
Full Changelog: JasperFx/marten@V8.34.2...V8.35.0
8.34.2
What's Changed
Patch release. One bug fix.
Money(decimal Value, Guid CurrencyId), the LINQ resolver would throwBadLinqExpressionExceptionon any nested member access (x.MoneyProp.Amount > 0). Root cause wasValueTypeIdGeneration.IsCandidatefiltering properties only to those inDocumentMapping.ValidIdTypes(Guid/int/long/string), so a multi-field struct with a single matching property + a staticZero(Guid)builder got misdetected as a strong-typed-id wrapper. As a side effect the misdetection registeredMoneyas auuidcolumn on Weasel's globalPostgresqlProvider.Instance, poisoning LINQ resolution for the rest of the process. Fix: reject types whose canonical constructor takes more than one parameter before any further matching. Reported with full root-cause analysis by @mmidkiff.Full Changelog: JasperFx/marten@V8.34.1...V8.34.2
8.34.1
What's Changed
Patch release. Two fixes — one regression in the cold-start path, one Scoped-subscription bug that's been latent since
AddSubscriptionWithServicesshipped.CultureNotFoundExceptionatDocumentStore..ctoron hosts running with<InvariantGlobalization>true</InvariantGlobalization>(implied by<PublishAot>true</PublishAot>). The cold-start prefilter inProjectionGraph.IsAssemblyKnownToHaveNoEvolverswas readingassembly.GetName().Name, which under invariant-globalization mode throws on culture-tagged satellite assemblies likept-br. Reported today against the cold-start optimization changes that landed in 8.34.0.AddSubscriptionWithServices<T>(ServiceLifetime.Scoped, configure)setOptions.BatchSize,Options.SubscribeFromPresent(),Name, orVersionin its constructor, those values were silently lost. OnlyIncludedEventTypes,StreamType, andIncludeArchivedEventswere copied from the resolved innerTto the wrapper. The Singleton path was unaffected. Thanks to @Casper-Olsen for the root-cause analysis.Full Changelog: JasperFx/marten@V8.34.0...V8.34.1
8.34.0
What's Changed
This release rolls in the JasperFx 1.28 / JasperFx.Events 1.31 upgrade chain, several cold-start and runtime-perf optimizations, two stability fixes (advisory locks, projection version suffix), and a new declarative ancillary-store enrichment API.
Full Changelog: JasperFx/marten@V8.33.0...V8.34.0
8.33.0
What's Changed
New Contributors
Full Changelog: JasperFx/marten@V8.32.1...V8.33.0
Commits viewable in compare view.
Updated Marten.EntityFrameworkCore from 8.32.1 to 8.36.0.
Release notes
Sourced from Marten.EntityFrameworkCore's releases.
8.36.0
Highlights
Marten 8.36.0 closes out #4329 by adopting JasperFx.Events 1.35.0 and ships the corresponding docs and integration tests, plus a separately-tracked docs improvement for modular
IConfigureMartenprojection registration (#4326) and two LINQ fixes.Options.CacheLimitPerTenantis a memory tunable again, not a correctness lever for downstreamEnrichWith<T>/TryFindUpstreamCachelookups.ForEntityIdsfor fan-out enrichment (via JasperFx.Events 1.35.0). New first-class declarative shape for events that reference several entities of the same type:composite.mdcalls out that downstream stages can't SQL-query upstream stages' in-flight writes, lists the four supported alternatives (Updated<T>synthetic events,EnrichWith<T>().AddReferences(),TryFindUpstreamCache<TId, T>,ReferencePeerView<T>), and includes inline samples sourced from the integration tests.IConfigureMarten+ DI projection registration docs. New section inevents/projections/ioc.mdshowing how a module-style configuration can register a service-aware projection by taking its dependencies through theIConfigureMartenconstructor and building the projection insideConfigure(...). Closes #4326.string[].Containsparse failure under C# 14 + nullable + method init (#4332), andWhereclauses on the inner source ofGroupJoinare now honored.What's Changed
Whereclauses on the inner source ofGroupJoinby @snrnats in HonorWhereclauses on the inner source ofGroupJoinJasperFx/marten#4331New Contributors
Whereclauses on the inner source ofGroupJoinJasperFx/marten#4331Full Changelog: JasperFx/marten@V8.35.0...V8.36.0
8.35.0
Heads up, this will cause a DDL change for some upsert functions due to a bug that was only apparent under high concurrency
What's Changed
Full Changelog: JasperFx/marten@V8.34.2...V8.35.0
8.34.2
What's Changed
Patch release. One bug fix.
Money(decimal Value, Guid CurrencyId), the LINQ resolver would throwBadLinqExpressionExceptionon any nested member access (x.MoneyProp.Amount > 0). Root cause wasValueTypeIdGeneration.IsCandidatefiltering properties only to those inDocumentMapping.ValidIdTypes(Guid/int/long/string), so a multi-field struct with a single matching property + a staticZero(Guid)builder got misdetected as a strong-typed-id wrapper. As a side effect the misdetection registeredMoneyas auuidcolumn on Weasel's globalPostgresqlProvider.Instance, poisoning LINQ resolution for the rest of the process. Fix: reject types whose canonical constructor takes more than one parameter before any further matching. Reported with full root-cause analysis by @mmidkiff.Full Changelog: JasperFx/marten@V8.34.1...V8.34.2
8.34.1
What's Changed
Patch release. Two fixes — one regression in the cold-start path, one Scoped-subscription bug that's been latent since
AddSubscriptionWithServicesshipped.CultureNotFoundExceptionatDocumentStore..ctoron hosts running with<InvariantGlobalization>true</InvariantGlobalization>(implied by<PublishAot>true</PublishAot>). The cold-start prefilter inProjectionGraph.IsAssemblyKnownToHaveNoEvolverswas readingassembly.GetName().Name, which under invariant-globalization mode throws on culture-tagged satellite assemblies likept-br. Reported today against the cold-start optimization changes that landed in 8.34.0.AddSubscriptionWithServices<T>(ServiceLifetime.Scoped, configure)setOptions.BatchSize,Options.SubscribeFromPresent(),Name, orVersionin its constructor, those values were silently lost. OnlyIncludedEventTypes,StreamType, andIncludeArchivedEventswere copied from the resolved innerTto the wrapper. The Singleton path was unaffected. Thanks to @Casper-Olsen for the root-cause analysis.Full Changelog: JasperFx/marten@V8.34.0...V8.34.1
8.34.0
What's Changed
This release rolls in the JasperFx 1.28 / JasperFx.Events 1.31 upgrade chain, several cold-start and runtime-perf optimizations, two stability fixes (advisory locks, projection version suffix), and a new declarative ancillary-store enrichment API.
Full Changelog: JasperFx/marten@V8.33.0...V8.34.0
8.33.0
What's Changed
New Contributors
Full Changelog: JasperFx/marten@V8.32.1...V8.33.0
Commits viewable in compare view.
Updated SonarAnalyzer.CSharp from 10.24.0.138807 to 10.25.0.139117.
Release notes
Sourced from SonarAnalyzer.CSharp's releases.
10.25
?
Feature
sonar.cs.cobertura.reportsPathsparameterFalse Positive
Commits viewable in compare view.
Updated WolverineFx from 5.32.1 to 5.37.2.
Release notes
Sourced from WolverineFx's releases.
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
5.36.1
Upgrade to this version please if you use the EF Core transactional middleware and are using a very recent version of Wolverine
What's Changed
Full Changelog: JasperFx/wolverine@V5.36.0...v5.36.1
5.36.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.35.2...V5.36.0
5.35.2
What's Changed
A small bug-fix and dependency-refresh release.
Persistence fixes
OracleMessageStore.Initializeand the surrounding schema declared timestamp columns (health_check,started,posted, etc.) with a DEFAULT ofSYS_EXTRACT_UTC(SYSTIMESTAMP). That returns a TIMESTAMP without a time zone, and when implicitly cast into theTIMESTAMP WITH TIME ZONEcolumn Oracle stamps it with the session time zone — so for any session in UTC+N the just-persisted value's UTC equivalent was N hours in the past. That tripped theNodeAgentController.DoHealthChecksAsyncstaleness filter and surfaced as aNullReferenceExceptionduring the first leadership-election heartbeat (self!.AssignAgents([LeaderUri])on anullself). All 18 occurrences swapped toSYSTIMESTAMP AT TIME ZONE 'UTC', with quote-doubling for the DDL contexts that go through Weasel'sEXECUTE IMMEDIATE '...'wrapper.Reliability hardening
dbcontrol://andoraclecontrol://endpoints toBufferedInMemory(#2637) — the database-backed control transport carries inter-node leader-election and agent-reassignment commands. Marking either endpoint Durable would route every control envelope through the same store-backed inbox/outbox the durability agent itself owns (deadlock); marking it Inline contradicts the batched-poll semantics. BothDatabaseControlEndpointandOracleControlEndpointnow overridesupportsModeso any policy that tries to flip them offBufferedInMemoryeither silently skips (UseDurableInboxOnAllListeners,UseDurableOutboxOnAllSendingEndpoints, etc., already checkSupportsMode) or fails fast with a clearInvalidOperationException.Source-gen / startup
IWolverineTypeLoaderacross all known assemblies (#2632) by @devployment — since 5.34.0, hosts on the source-generated codegen path silently dropped handlers that lived in referenced assemblies becausetryDiscoverTypeLoaderFromAttributeonly inspectedOptions.ApplicationAssembly. First invocation of one of those handlers threwIndeterminateRoutesException. The runtime now walksApplicationAssemblyand every assembly inDiscovery.Assemblies, collects every[WolverineTypeManifest]loader it finds, and exposes their union via the new internalCompositeWolverineTypeLoader. Existing single-loader semantics are preserved when only one manifest is found.Other
Dependencies
Full Changelog: JasperFx/wolverine@V5.35.1...V5.35.2
5.35.1
What's Changed
A bug-fix and small-feature release covering Oracle-in-Balanced-mode startup, a duplicate-poller defect on RavenDb, an AWS SQS sharded-slot naming fix, and a new SagaDescriptor surface for CritterWatch.
Persistence fixes
Oracle in
DurabilityMode.Balancednow boots (#2622) —OracleMessageStore.Initializewas a no-op, so hosts using Oracle persistence in Balanced mode failed to start withArgumentOutOfRangeException("ControlEndpoint cannot be null for this usage"). The fix mirrorsMessageDatabase.Initializefor Oracle and stands up a parallelOracleControlTransport/OracleControlEndpoint/OracleControlSender/OracleControlListenerset under the neworaclecontrol://protocol — necessary because the sharedDatabaseControlSender/DatabaseControlListenerassume@-prefixed placeholders and Guid values that map directly onto aDbParameter, neither of which Oracle accepts (:-prefixed placeholders,RAW(16)id columns requiringbyte[]). Also fixes a latentOracleMessageStore.EnqueueAsyncno-op that leftLogRecordsAsyncsilently dropping node records, and makesFetchRecentRecordsAsyncDBNull-safe on the description column. Adds a newOracleTests.LeaderElectionproject so the leadership-compliance suite runs against Oracle (marked[Trait("Category","Flaky")]because the suite needs careful TM/DML lock sequencing between back-to-back runs).RavenDb: only one durability agent polls after host start (#2623, #2629) by @Bishbulb (root-cause investigation and original fix) and @jeremydmiller —
RavenDbMessageStore.StartScheduledJobseagerly built and started aRavenDbDurabilityAgentat boot in addition to the agent thatNodeAgentControlleralready builds and starts viaIAgentFamily/MessageStoreCollection. TwoRavenDbDurabilityAgentinstances then polled the same database concurrently, both believed they held the scheduled-job lock, raced to mark the same envelopesIncoming, and surfacedConcurrencyExceptionplus double-fired timeouts. Drops the eagerStartTimers()call; the cluster-managed agent is now the single owner of polling. The agent returned fromStartScheduledJobsis held byWolverineRuntime.DurableScheduledJobspurely for its disposal-timeStopAsync. Comes with a reflection-free regression test (addedRavenDbDurabilityAgent.IsPollingandCompositeAgent.InnerAgentsfor the test to enumerate without poking at private fields). A companion regression-guard test for CosmosDb is included; investigation showed the equivalent CosmosDb path does NOT have the bug today (CosmosDbMessageStore.BuildAgentFamilyreturns null andUriuses thecosmosdb://scheme rather thanwolverinedb://, soMessageStoreCollectionnever registers a competing agent).Other improvements
AWS SQS: correct naming for sharded slot endpoints in #1f294ce5 — fixes a regression where sharded slot endpoint URIs were assembled with the wrong segment ordering, causing the consumer side to listen at the wrong queue.
SagaDescriptorexported viaServiceCapabilitiesin #f0998c7b — adds a saga-shape descriptor (saga type, id type, current state) to the capabilities exporter so CritterWatch can surface saga inventory and current state in its dashboard.Full Changelog: JasperFx/wolverine@V5.34.0...V5.35.1
5.34.0
What's Changed
This release introduces three new features (Claim Check pattern, declarative Polecat data requirements, and a new opt-in
WolverineFx.RuntimeCompilationpackage as the first step toward AOT compatibility), a fix for a long-standing service-location footgun, several real RavenDB and EF Core durability fixes, plus the cold-start prep work done as part of issue #1577.Highlights
[Blob]attribute (#2412) by @jeremydmiller in #2617 — off-load large message-property payloads to external storage on send and re-hydrate them on receive, so the on-the-wire envelope stays small. Core abstractions (IClaimCheckStore,ClaimCheckToken,[Blob],FileSystemClaimCheckStore,opts.UseClaimCheck(...)) live inWolverine.Persistence. Two new backend NuGet packages ship alongside:WolverineFx.ClaimCheck.AzureBlobStorageandWolverineFx.ClaimCheck.AmazonS3. New documentation page under/guide/durability/claim-checks.[DocumentExists<T>],[DocumentDoesNotExist<T>], andPolecatOps.Document<T>().MustExist(...)/.MustNotExist(...)mirror the Marten ergonomics, with the same batch-query optimization that folds multiple existence checks into a single PolecatIBatchedQueryround-trip.IMessageBus/IMessageContextnow see the active context (#2583) by @jeremydmiller in #2616 — when user code service-locatesIMessageBus(e.g., constructor injection on a service the handler resolves at runtime), it now receives the sameMessageContextthe handler itself uses, preserving outbox semantics. Implemented as a per-chain opt-in (gated onChain.UsesServiceLocation) so chains that don't service-locate pay zeroAsyncLocaloverhead per message.WolverineFx.RuntimeCompilationopt-in package (#1577) by @jeremydmiller in #2613 and #cc00ca0a — first pass at the cold-start / AOT roadmap. Wires theWolverine.SourceGenerationanalyzer into theWolverineFxNuGet output (so source-generatedIWolverineTypeLoaderdiscovery flows transitively to consumers), pre-populates theWolverineMessageNamingcache during startup to eliminate first-message reflection cost, applies[DynamicallyAccessedMembers]annotations on theActivator.CreateInstancecall sites for trimmer-friendliness, and addsConfigureAwait(false)across 117 awaits on the per-message hot path. The newWolverineFx.RuntimeCompilationpackage becomes the future-facing opt-in API for runtime Roslyn compilation; default behavior is preserved.RavenDB durability fixes
EF Core / ancillary stores
DurableLocalQueueto route incoming envelopes to ancillary stores (#2611) by @jeremydmiller — handler chains targeting an ancillary message store now have their incoming envelopes persisted in that store rather than the main store, fixing a class of "envelope stuck as Incoming forever" bugs.WolverineEnabledannotation collision in ancillary-store EF Core scenarios as part of #2618 —MapWolverineEnvelopeStorageis now idempotent when called against the same model graph more than once.Other improvements
MessageBusclobbering per-messageEnvelope.Sourcein #26e38002 —MessageBus.Sendwas overwriting the per-messageSourcewith the host'sServiceName, masking the originating service in causation tracking.ServiceLocationPolicy.NotAllowedv6 default (#2584) by @jeremydmiller in #2609 — chains that resolve dependencies via service location now log a warning at codegen time, with a clear migration path to the new opt-inWolverine.RuntimeCompilationstory for v6.CI stabilization
IDisposable→IAsyncLifetimeconversions, lifecycle cleanup; chronically broken-on-CI classes (SqliteTests.Transport.multi_tenancy_with_multiple_files,CosmosDbTests.LeaderElection.leader_election,Wolverine.RabbitMQ.Tests.send_by_topics,Wolverine.RabbitMQ.Tests.sending_raw_messages) tagged[Trait("Category", "Flaky")]with header comments documenting the symptom and the real follow-up fix.JasperFx.CodeGenerationandJasperFx.RuntimeCompilernow compile cleanly after theInitializeSynchronouslyextension method was moved intoJasperFx.CodeGenerationupstream.Issue-tracker housekeeping
#2507(Quartz.Net / TickerQ first-class integration) added to the 6.0 milestone with a phased plan documented on the issue.#1577(cold-start optimization roadmap) updated with a six-phase plan and current-state checklist; phases 1–4 are non-breaking on v5.x and largely landed in this release.Full Changelog: JasperFx/wolverine@V5.33.0...V5.34.0
5.33.0
What's Changed
This release includes a major reliability fix for distributed leader election, a port of the Polecat 2.x event store integration, and several other quality-of-life improvements.
Highlights
LeadershipLostnode record type and anIWolverineObserver.LostLeadership()hook for monitoring.JSONtype.Other Improvements
launchSettings.jsonto sample projects by @jeremydmiller in #2600Full Changelog: JasperFx/wolverine@V5.32.1...V5.33.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.32.1...V5.33.0
Commits viewable in compare view.
Updated WolverineFx.EntityFrameworkCore from 5.32.1 to 5.37.2.
Release notes
Sourced from WolverineFx.EntityFrameworkCore's releases.
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
5.36.1
Upgrade to this version please if you use the EF Core transactional middleware and are using a very recent version of Wolverine
What's Changed
Full Changelog: JasperFx/wolverine@V5.36.0...v5.36.1
5.36.0
What's Changed
Full Changelog: JasperFx/wolverine@V5.35.2...V5.36.0
5.35.2
What's Changed
A small bug-fix and dependency-refresh release.
Persistence fixes
OracleMessageStore.Initializeand the surrounding schema declared timestamp columns (health_check,started,posted, etc.) with a DEFAULT ofSYS_EXTRACT_UTC(SYSTIMESTAMP). That returns a TIMESTAMP without a time zone, and when implicitly cast into theTIMESTAMP WITH TIME ZONEcolumn Oracle stamps it with the session time zone — so for any session in UTC+N the just-persisted value's UTC equivalent was N hours in the past. That tripped theNodeAgentController.DoHealthChecksAsyncstaleness filter and surfaced as aNullReferenceExceptionduring the first leadership-election heartbeat (self!.AssignAgents([LeaderUri])on anullself). All 18 occurrences swapped toSYSTIMESTAMP AT TIME ZONE 'UTC', with quote-doubling for the DDL contexts that go through Weasel'sEXECUTE IMMEDIATE '...'wrapper.Reliability hardening
dbcontrol://andoraclecontrol://endpoints toBufferedInMemory(#2637) — the database-backed control transport carries inter-node leader-election and agent-reassignment commands. Marking either endpoint Durable would route every control envelope through the same store-backed inbox/outbox the durability agent itself owns (deadlock); marking it Inline contradicts the batched-poll semantics. BothDatabaseControlEndpointandOracleControlEndpointnow overridesupportsModeso any policy that tries to flip them offBufferedInMemoryeither silently skips (UseDurableInboxOnAllListeners,UseDurableOutboxOnAllSendingEndpoints, etc., already checkSupportsMode) or fails fast with a clearInvalidOperationException.Source-gen / startup
IWolverineTypeLoaderacross all known assemblies (#2632) by @devployment — since 5.34.0, hosts on the source-generated codegen path silently dropped handlers that lived in referenced assemblies becausetryDiscoverTypeLoaderFromAttributeonly inspectedOptions.ApplicationAssembly. First invocation of one of those handlers threwIndeterminateRoutesException. The runtime now walksApplicationAssemblyand every assembly inDiscovery.Assemblies, collects every[WolverineTypeManifest]loader it finds, and exposes their union via the new internalCompositeWolverineTypeLoader. Existing single-loader semantics are preserved when only one manifest is found.Other
Dependencies
Full Changelog: JasperFx/wolverine@V5.35.1...V5.35.2
5.35.1
What's Changed
A bug-fix and small-feature release covering Oracle-in-Balanced-mode startup, a duplicate-poller defect on RavenDb, an AWS SQS sharded-slot naming fix, and a new SagaDescriptor surface for CritterWatch.
Persistence fixes
Oracle in
DurabilityMode.Balancednow boots (#2622) —OracleMessageStore.Initializewas a no-op, so hosts using Oracle persistence in Balanced mode failed to start withArgumentOutOfRangeException("ControlEndpoint cannot be null for this usage"). The fix mirrorsMessageDatabase.Initializefor Oracle and stands up a parallelOracleControlTransport/OracleControlEndpoint/OracleControlSender/OracleControlListenerset under the neworaclecontrol://protocol — necessary because the sharedDatabaseControlSender/DatabaseControlListenerassume@-prefixed placeholders and Guid values that map directly onto aDbParameter, neither of which Oracle accepts (:-prefixed placeholders,RAW(16)id columns requiringbyte[]). Also fixes a latentOracleMessageStore.EnqueueAsyncno-op that leftLogRecordsAsyncsilently dropping node records, and makesFetchRecentRecordsAsyncDBNull-safe on the description column. Adds a newOracleTests.LeaderElectionproject so the leadership-compliance suite runs against Oracle (marked[Trait("Category","Flaky")]because the suite needs careful TM/DML lock sequencing between back-to-back runs).RavenDb: only one durability agent polls after host start (#2623, #2629) by @Bishbulb (root-cause investigation and original fix) and @jeremydmiller —
RavenDbMessageStore.StartScheduledJobseagerly built and started aRavenDbDurabilityAgentat boot in addition to the agent thatNodeAgentControlleralready builds and starts viaIAgentFamily/MessageStoreCollection. TwoRavenDbDurabilityAgentinstances then polled the same database concurrently, both believed they held the scheduled-job lock, raced to mark the same envelopesIncoming, and surfacedConcurrencyExceptionplus double-fired timeouts. Drops the eagerStartTimers()call; the cluster-managed agent is now the single owner of polling. The agent returned fromStartScheduledJobsis held byWolverineRuntime.DurableScheduledJobspurely for its disposal-timeStopAsync. Comes with a reflection-free regression test (addedRavenDbDurabilityAgent.IsPollingandCompositeAgent.InnerAgentsfor the test to enumerate without poking at private fields). A companion regression-guard test for CosmosDb is included; investigation showed the equivalent CosmosDb path does NOT have the bug today (CosmosDbMessageStore.BuildAgentFamilyreturns null andUriuses thecosmosdb://scheme rather thanwolverinedb://, soMessageStoreCollectionnever registers a competing agent).Other improvements
AWS SQS: correct naming for sharded slot endpoints in #1f294ce5 — fixes a regression where sharded slot endpoint URIs were assembled with the wrong segment ordering, causing the consumer side to listen at the wrong queue.
SagaDescriptorexported viaServiceCapabilitiesin #f0998c7b — adds a saga-shape descriptor (saga type, id type, current state) to the capabilities exporter so CritterWatch can surface saga inventory and current state in its dashboard.Full Changelog: JasperFx/wolverine@V5.34.0...V5.35.1
5.34.0
What's Changed
This release introduces three new features (Claim Check pattern, declarative Polecat data requirements, and a new opt-in
WolverineFx.RuntimeCompilationpackage as the first step toward AOT compatibility), a fix for a long-standing service-location footgun, several real RavenDB and EF Core durability fixes, plus the cold-start prep work done as part of issue #1577.Highlights
[Blob]attribute (#2412) by @jeremydmiller in #2617 — off-load large message-property payloads to external storage on send and re-hydrate them on receive, so the on-the-wire envelope stays small. Core abstractions (IClaimCheckStore,ClaimCheckToken,[Blob],FileSystemClaimCheckStore,opts.UseClaimCheck(...)) live inWolverine.Persistence. Two new backend NuGet packages ship alongside:WolverineFx.ClaimCheck.AzureBlobStorageandWolverineFx.ClaimCheck.AmazonS3. New documentation page under/guide/durability/claim-checks.[DocumentExists<T>],[DocumentDoesNotExist<T>], andPolecatOps.Document<T>().MustExist(...)/.MustNotExist(...)mirror the Marten ergonomics, with the same batch-query optimization that folds multiple existence checks into a single PolecatIBatchedQueryround-trip.IMessageBus/IMessageContextnow see the active context (#2583) by @jeremydmiller in #2616 — when user code service-locatesIMessageBus(e.g., constructor injection on a service the handler resolves at runtime), it now receives the sameMessageContextthe handler itself uses, preserving outbox semantics. Implemented as a per-chain opt-in (gated onChain.UsesServiceLocation) so chains that don't service-locate pay zeroAsyncLocaloverhead per message.WolverineFx.RuntimeCompilationopt-in package (#1577) by @jeremydmiller in #2613 and #cc00ca0a — first pass at the cold-start / AOT roadmap. Wires theWolverine.SourceGenerationanalyzer into theWolverineFxNuGet output (so source-generatedIWolverineTypeLoaderdiscovery flows transitively to consumers), pre-populates theWolverineMessageNamingcache during startup to eliminate first-message reflection cost, applies[DynamicallyAccessedMembers]annotations on theActivator.CreateInstancecall sites for trimmer-friendliness, and addsConfigureAwait(false)across 117 awaits on the per-message hot path. The newWolverineFx.RuntimeCompilationpackage becomes the future-facing opt-in API for runtime Roslyn compilation; default behavior is preserved.RavenDB durability fixes
EF Core / ancillary stores
DurableLocalQueueto route incoming envelopes to ancillary stores (#2611) by @jeremydmiller — handler chains targeting an ancillary message store now have their incoming envelopes persisted in that store rather than the main store, fixing a class of "envelope stuck as Incoming forever" bugs.WolverineEnabledannotation collision in ancillary-store EF Core scenarios as part of #2618 —MapWolverineEnvelopeStorageis now idempotent when called against the same model graph more than once.Other improvements
MessageBusclobbering per-messageEnvelope.Sourcein #26e38002 —MessageBus.Sendwas overwriting the per-messageSourcewith the host'sServiceName, masking the originating service in causation tracking.ServiceLocationPolicy.NotAllowedv6 default (#2584) by @jeremydmiller in #2609 — chains that resolve dependencies via service location now log a warning at codegen time, with a clear migration path to the new opt-inWolverine.RuntimeCompilationstory for v6.CI stabilization
IDisposable→IAsyncLifetimeconversions, lifecycle cleanup; chronically broken-on-CI classes (SqliteTests.Transport.multi_tenancy_with_multiple_files,CosmosDbTests.LeaderElection.leader_election,Wolverine.RabbitMQ.Tests.send_by_topics,Wolverine.RabbitMQ.Tests.sending_raw_messages) tagged[Trait("Category", "Flaky")]with header comments documenting the symptom and the real follow-up fix.JasperFx.CodeGenerationandJasperFx.RuntimeCompilernow compile cleanly after theInitializeSynchronouslyextension method was moved intoJasperFx.CodeGenerationupstream.Issue-tracker housekeeping
#2507(Quartz.Net / TickerQ first-class integration) added to the 6.0 milestone with a phased plan documented on the issue.#1577(cold-start optimization roadmap) updated with a six-phase plan and current-state checklist; phases 1–4 are non-breaking on v5.x and largely landed in this release.Full Changelog: JasperFx/wolverine@V5.33.0...V5.34.0
5.33.0
What's Changed
This release includes a major reliability fix for distributed leader election, a port of the Polecat 2.x event store integration, and several other quality-of-life improvements.
Highlights
LeadershipLostnode record type and anIWolverineObserver.LostLeadership()hook for monitoring.JSONtype.Other Improvements
launchSettings.jsonto sample projects by @jeremydmiller in #2600Full Changelog: JasperFx/wolverine@V5.32.1...V5.33.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V5.32.1...V5.33.0
Commits viewable in compare view.
Updated WolverineFx.Marten from 5.32.1 to 5.37.2.
Release notes
Sourced from WolverineFx.Marten's releases.
5.37.2
What's Changed
Full Changelog: JasperFx/wolverine@V5.37.0...V5.37.2
5.37.0
What's Changed
Full Changelog: JasperFx/wolverine@v5.36.1...V5.37.0
5.36.1
Upgrade to this version please if you use the EF Core transactional middleware and are using a very recent version of Wolverine
What's Changed
Full Changelog: JasperFx/wolverine@V5.36.0...v5.36.1
5.36.0
What's Changed
...
Description has been truncated