Bump the nuget-minor-and-patch group with 25 updates by dependabot[bot] · Pull Request #15 · tthanhtung92/finmy

This release improves generic call matching (#989, #974, #990). Thanks to @zvirja and @JMolenkamp for fixes this.
We've also switched to using trusted nuget publishing linked to GitHub Releases. (#987, @zvirja)

What's Changed

Add trusted nuget publish by @zvirja in Add trusted nuget publish nsubstitute/NSubstitute#987
fix: Stop using return-type assignability for generic call matching by @zvirja in fix: Stop using return-type assignability for generic call matching nsubstitute/NSubstitute#989
Remove skip-duplicate option from NuGet push command by @zvirja in Remove skip-duplicate option from NuGet push command nsubstitute/NSubstitute#988
Add tag trigger for release pipeline by @zvirja in Add tag trigger for release pipeline nsubstitute/NSubstitute#991
Fix broken comparison of the generic methods by @zvirja in Fix broken comparison of the generic methods nsubstitute/NSubstitute#990
Support C# 13 params collections in argument matching by @zvirja in Support C# 13 params collections in argument matching nsubstitute/NSubstitute#993
Add tests for nullable Task by @zvirja in Add tests for nullable Task nsubstitute/NSubstitute#994

Full Changelog: nsubstitute/NSubstitute@v6.1.0...v6.2.0

6.1.0

NSubstitute v6.1.0

This release reverts nullability support introduced in 6.0. This change caused a number of problems for callers (#973, #976), and trying to resolve these (#976) revealed the need for more fundamental changes to NSubstitute to effectively support this. As a result, nullability is again disabled for public API. Huge thanks to @jdb0123, @Romfos, and @Moha-sami for their PRs addressing this, and thanks for all those who raised issues. We also humbly award @zvirja with one unlimited "I told you so" pass to use as he sees fit.

What's Changed

Add new argument matcher for comparing objects by reference by @Wer-Wolf in Add new argument matcher for comparing objects by reference nsubstitute/NSubstitute#963
Revert nullability changes in Revert nullability changes nsubstitute/NSubstitute#985

New Contributors

@Wer-Wolf made their first contribution in Add new argument matcher for comparing objects by reference nsubstitute/NSubstitute#963

Full Changelog: nsubstitute/NSubstitute@v6.0.0...v6.1.0

Commits viewable in compare view.

Updated Roslynator.Analyzers from 4.15.0 to 4.16.1.

Release notes

Sourced from Roslynator.Analyzers's releases.

4.16.1

Fixed

Fix analyzer RCS1060 to not report a file that contains only multiple partial declarations of the same type (PR)
Fix analyzer RCS1231 to not suggest in for ref struct parameters (#1725) (PR)
Fix analyzer RCS1260 false positive for omit_when_single_line on multi-line object/collection initializers (#1439) (PR)
Fix analyzer RCS0036 to report blank lines between single-line declarations in records (PR)
Fix analyzer RCS1046 to report async void methods without Async suffix (PR)
Fix analyzer RCS1265 to not report catch clauses with a when filter (PR)
Fix analyzer RCS0034 for types with a primary constructor and multiple constraint clauses (PR)
Fix analyzer RCS1231 to not report CancellationToken in sync methods returning Task (PR)
[CLI] Fix GitLab output format to use relative paths, forward slashes, and 1-based line numbers (PR)
[CLI] Fix generate-doc to omit internal interfaces from type declarations and the Implements section (PR)

4.16.0

Added

[CLI] Suppress error code from Roslynator when it detects issues in code but runs successfully (PR by @mdrybak)

Fixed

Fix analyzer RCS1118 to not report local variable passed as 'in' argument (PR by @NoahStolk)
Fix analyzer RCS1074 (PR by @cbersch)
Fix enum contained flags check for partial matches in RCS1258 (PR by @ovska)
Fix analyzer RCS1146 (PR)
Fix analyzer RCS1194 (PR)
Fix analyzer RCS1060 to ignore classes marked with file modifier (PR by @cbersch)
Fix analyzer RCS1231 (PR by @cbersch)
Fix analyzer RCS1246 for conditional access expressions ([PR](Fix analyzer RCS1246 for conditional access expressions dotnet/roslynator#1772 by @krajek))
[CLI] Fix fix command ignoring --include / --exclude file filter (PR by @hashiiiii)
[CLI] Fix loading of projects and solutions on .NET 10 SDK (PR)

Commits viewable in compare view.

Updated Scalar.AspNetCore from 2.16.16 to 2.16.20.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated SonarAnalyzer.CSharp from 10.31.0.145097 to 10.32.0.713.

Release notes

Sourced from SonarAnalyzer.CSharp's releases.

10.32.0.713

Release notes - .NET Analyzers - 10.32

Feature

NET-4132 Implement rule S9022: Redundant "Include" calls should be removed
NET-4215 Implement rule S9118: Default values should be compatible with their entity property type
NET-4240 Update RSPEC before 10.32 release

False Positive

NET-1322 Fix S2857 FP: Do not raise in constant string interpolation when string is in square brackets
NET-1468 Fix S6966 FP: should not raise when inside lock
NET-1598 Fix S1125 FP: dynamic and custom nullable structs with conversion to bool are compliant
NET-4233 Fix S8733 FP: AsSplitQuery/AsSingleQuery set in a different statement than the colliding Includes goes undetected
NET-4297 Fix S8717 FP: EFCore DBFirst Scaffold

Commits viewable in compare view.

Updated Testcontainers.Minio from 4.13.0 to 4.14.0.

Release notes

Sourced from Testcontainers.Minio's releases.

4.14.0

What's Changed

I published this version because several developers asked for a release addressing the SSH.NET vulnerability. As an interim fix, you can also bump the transitive dependency, which should work fine.

Unfortunately, I had to run the release CI pipeline twice (1, 2). The change #1725 introduced a regression that caused the pipeline to attempt to publish the Cake build project, which correctly failed (partially published).

The NuGet packages for this release have been attested for supply chain security using actions/attest. This confirms the integrity and provenance of the artifacts and helps ensure they can be trusted: #40693051.

🚀 Features

feat: Add possibility to select MSSQL database (instead of master) (#1737) @0xced, @HofmeisterAn
feat: Add Mailpit module (#1727) @0xced, @feslima, @HofmeisterAn

🐛 Bug Fixes

fix(MongoDb): Probe the server instead of counting log messages before initiating (#1735) @arnelirobles, @HofmeisterAn
fix(MongoDb): Treat an already initiated replica set as success (#1731) @arnelirobles, @HofmeisterAn

🧹 Housekeeping

chore: Cleanup and align tests (#1740) @HofmeisterAn
chore: Set Cake build solution file path to Testcontainers.slnx (#1728) @0xced
chore: Keep Testcontainers.slnx solution file only (#1725) @0xced
feat: Prepare next release cycle (4.14.0) (#1726) @HofmeisterAn

📦 Dependency Updates

chore(deps): Bump SSH.NET to 2026.0.0 and BouncyCastle.Cryptography to 2.7.0 (#1739) @markmario
chore(deps): Bump the actions group with 10 updates (#1730) @dependabot[bot]

Commits viewable in compare view.

Updated Testcontainers.PostgreSql from 4.13.0 to 4.14.0.

Release notes

Sourced from Testcontainers.PostgreSql's releases.

4.14.0

What's Changed

I published this version because several developers asked for a release addressing the SSH.NET vulnerability. As an interim fix, you can also bump the transitive dependency, which should work fine.

Unfortunately, I had to run the release CI pipeline twice (1, 2). The change #1725 introduced a regression that caused the pipeline to attempt to publish the Cake build project, which correctly failed (partially published).

The NuGet packages for this release have been attested for supply chain security using actions/attest. This confirms the integrity and provenance of the artifacts and helps ensure they can be trusted: #40693051.

🚀 Features

feat: Add possibility to select MSSQL database (instead of master) (#1737) @0xced, @HofmeisterAn
feat: Add Mailpit module (#1727) @0xced, @feslima, @HofmeisterAn

🐛 Bug Fixes

fix(MongoDb): Probe the server instead of counting log messages before initiating (#1735) @arnelirobles, @HofmeisterAn
fix(MongoDb): Treat an already initiated replica set as success (#1731) @arnelirobles, @HofmeisterAn

🧹 Housekeeping

chore: Cleanup and align tests (#1740) @HofmeisterAn
chore: Set Cake build solution file path to Testcontainers.slnx (#1728) @0xced
chore: Keep Testcontainers.slnx solution file only (#1725) @0xced
feat: Prepare next release cycle (4.14.0) (#1726) @HofmeisterAn

📦 Dependency Updates

chore(deps): Bump SSH.NET to 2026.0.0 and BouncyCastle.Cryptography to 2.7.0 (#1739) @markmario
chore(deps): Bump the actions group with 10 updates (#1730) @dependabot[bot]

Commits viewable in compare view.

Updated Testcontainers.Redis from 4.13.0 to 4.14.0.

Release notes

Sourced from Testcontainers.Redis's releases.

4.14.0

What's Changed

I published this version because several developers asked for a release addressing the SSH.NET vulnerability. As an interim fix, you can also bump the transitive dependency, which should work fine.

Unfortunately, I had to run the release CI pipeline twice (1, 2). The change #1725 introduced a regression that caused the pipeline to attempt to publish the Cake build project, which correctly failed (partially published).

The NuGet packages for this release have been attested for supply chain security using actions/attest. This confirms the integrity and provenance of the artifacts and helps ensure they can be trusted: #40693051.

🚀 Features

feat: Add possibility to select MSSQL database (instead of master) (#1737) @0xced, @HofmeisterAn
feat: Add Mailpit module (#1727) @0xced, @feslima, @HofmeisterAn

🐛 Bug Fixes

fix(MongoDb): Probe the server instead of counting log messages before initiating (#1735) @arnelirobles, @HofmeisterAn
fix(MongoDb): Treat an already initiated replica set as success (#1731) @arnelirobles, @HofmeisterAn

🧹 Housekeeping

chore: Cleanup and align tests (#1740) @HofmeisterAn
chore: Set Cake build solution file path to Testcontainers.slnx (#1728) @0xced
chore: Keep Testcontainers.slnx solution file only (#1725) @0xced
feat: Prepare next release cycle (4.14.0) (#1726) @HofmeisterAn

📦 Dependency Updates

chore(deps): Bump SSH.NET to 2026.0.0 and BouncyCastle.Cryptography to 2.7.0 (#1739) @markmario
chore(deps): Bump the actions group with 10 updates (#1730) @dependabot[bot]

Commits viewable in compare view.

Updated WolverineFx from 6.22.0 to 6.29.0.

Release notes

Sourced from WolverineFx's releases.

6.29.0

A feature release. Three of the five items fix silent failure modes — work that acted on a write which could still roll back, a convention mirror that installed a relay over a real handler, and two concurrent writers to one entity — so the notes below say what the old behaviour looked like, not just what changed.

`AfterCommit` — run work after the transactional commit

After reads like a post-handler hook that runs at the end. It does not run after the commit (#3976, closes #3975).

The commit is itself a postprocessor contributed by the persistence provider, and After methods are inserted at the front of that list. So an After method observing a write is observing one that is not durable yet and may still roll back — and there was no supported way to ask for the other side of it, even though Wolverine uses that position itself for the outbox flush.

public static class RaiseAlertHandler
{
    public static void Handle(RaiseAlert command, IDocumentSession session)
        => session.Events.Append(command.Id, new AlertRaised(command.Reason));

    // Only runs if the append above actually committed
    public static void AfterCommit(AlertLatch latch, RaiseAlert command)
        => latch.MarkRaised(command.Id);
}

Use the AfterCommit / AfterCommitAsync convention or [WolverineAfterCommit], on message handlers, sagas and HTTP endpoints. Parameters bind exactly as After already does.

The position is structural, not positional — frames go into a new IChain.PostCommitPostprocessors list concatenated after every postprocessor at frame-assembly time, rather than being appended from a policy sequenced after the persistence policy. Getting the position right by luck of policy ordering is precisely what breaks silently later.

Two behaviours worth knowing:

They do not run when the commit throws. Frames are concatenated without a try/finally, so the exception unwinds straight past them. That is the point — the reason to want "after the commit" is usually that the side effect must not happen for a write that did not land.
They run after the outbox flush as well, so a message cascaded from an after-commit method is not atomic with the write. Cascade from the handler if it has to be.

After's pre-commit position is unchanged and stays that way. Verified per provider: Marten, Polecat, Fisher, EF Core, RavenDb and CosmosDb each have a codegen test asserting the emitted call lands after that provider's own commit frame.

A store-agnostic `EventsToAppend` return type

Wolverine.Marten.Events, Wolverine.Polecat.Events and Wolverine.Fisher.Events are identical but store-named, so a handler that wanted to be store-agnostic could not name any of them (#3969, closes #3941).

The store-agnostic path did exist — a bare IEnumerable<object> return is picked up by a fallback — but that fallback is positional. IEnumerable<T> is covariant, so every reference-typed collection in a return tuple is a candidate and the first one wins. Nothing failed at codegen and nothing failed at runtime; the wrong collection simply became the appended events.

The type is EventsToAppend, not Events. Naming it Events would have been a source-breaking collision (CS0104) for any handler importing both the core event-sourcing namespace and a store integration — that is, on the very declaration the feature exists for.

Ask what will be handled, and how a batch is shaped

Discovery materializes after options time, so an extension installing fallback handlers could not ask "will this message type have a handler?" and had to hand-roll a mirror of Wolverine's own discovery convention (#3977, closes #3974).

Such a mirror drifts, and it drifts silently: one that scanned a single assembly stopped seeing handlers that moved to a second, and installed a bare relay over a real handler — the exact defect the guard existed to prevent, with every codegen test still passing.

opts.OnHandlersDiscovered(handlers =>
{
    if (!handlers.Handles<ServiceUpdates>())
    {
 ... (truncated)

## 6.28.2

A bug fix release, with one new opt-in on the RabbitMQ listener contributed by the community.

## Store agnostic document sessions

A handler can now take the `JasperFx.Events.Documents` contracts — `IDocumentSessionOperations`, `IDocumentWriteOperations`, `IDocumentReadOperations` — straight as parameters, and they bind *and commit* on Marten, Polecat and Fisher alike ([#3962](https://github.com/JasperFx/wolverine/pull/3962), closes [#3956](https://github.com/JasperFx/wolverine/issues/3956)):

```csharp
// Valid against all three stores -- nothing store specific is named
public static void Handle(RecordNote command, IDocumentSessionOperations session)
    => session.Store(new Note { Id = command.Id, Text = command.Text });

These are the document side counterparts to the IEventOperations contracts Wolverine already understood, and they are the only way store agnostic source can take a session without naming a concrete store type.

Before this, such a handler failed codegen outright on a stock host. Once bound, its writes were queued into the session's unit of work and silently discarded — no exception. Both halves are fixed.

⚠️ Importing the JasperFx.Events.Documents namespace makes ToListAsync() ambiguous with each store's own queryable extensions (CS0121). Alias the individual contracts rather than importing the namespace.

Durability agents no longer assigned to nodes that cannot run them

A node started with Durability.DurabilityAgentEnabled = false never registers the durability agent family, so it threw Unrecognized agent scheme 'wolverinedb' the moment the leader handed it one. The leader re-issued the identical assignment every five minutes indefinitely, no durability agent ran anywhere for that store, and owner_id = 0 outgoing envelopes were never recovered (#3963, closes #3954).

The failure was silent in both directions — every queue table read zero while the backlog grew. Nodes now publish a marker capability when the family is actually registered, the leader skips nodes that have not, and when no node in the cluster is capable a warning names the condition and the setting.

If you run a Balanced cluster with DurabilityAgentEnabled = false on any node, this release is worth taking.

Ancillary store transaction ownership

Ancillary store inference scanned chain.ServiceDependencies(), which walks constructor graphs recursively — so a dependency that merely held an ancillary store matched. A read only store injected two hops down counted the same as an injected DbContext, and a tenant Marten handler had its inbox and dead letters stolen by the wrong store (#3957, closes #3953).

That inference was only ever correct for EF Core. There is a new default null IPersistenceFrameProvider.TryDetermineTransactionOwnerType for it, implemented only by EF Core.

RabbitMQ

Wait for prefetched messages on drain (#3796) — contributed by @benjamin-alexander-simplisafe. Opt in with ListenToRabbitQueue("orders").DrainWaitForPrefetch() to let already prefetched messages finish rather than letting the broker requeue them.
The prefetch drain is safe for a non terminal stop (#3960) — StopAsync is not always terminal, and a BatchingChannel silently discards a post after completion, so a delivery landing between the drain and the dispose latch vanished and was redelivered.
A rejected settle quiesces the channel the broker already closed (#3964, addresses #3950) — feeding a channel that is being torn down is what makes RabbitMQ.Client race itself and escalate a dead channel into a close of the entire connection (code=541). This narrows the window and speeds recovery; it does not prevent the close, whose root cause is upstream in rabbitmq-dotnet-client.
Listener recovery after a mid flight connection death is now asserted (#3961).

Idle reaper no longer latches durable endpoints

A durable endpoint reached only via EndpointFor(uri) looked as disposable as an ephemeral reply queue and was reaped; the rebuilt agent then wrapped a disposed sender and latched forever (#3958, closes #3955). SendingAgentIdleTimeout had no test coverage at all before this.

6.28.1

Patch release over 6.28.0.

New package

WolverineFx.Http.Fisher (#3949, closes #3944) — there was a Wolverine.Http.Marten and a Wolverine.Http.Polecat and no Fisher equivalent, so a Fisher-backed application had nothing to reference for the aggregate/document HTTP attributes. The third flavour now exists alongside its siblings.

Fixes

A SQLite "schema name" is now the table name prefix it was documented to be

(#3945, closes #3943)

Setting FisherIntegration.MessageStorageSchemaName, or the schemaName argument to PersistMessagesWithSqlite(), reached the message store as a schema.table qualifier. SQLite has no user-defined schemas — the only names a plain connection knows are main, temp, and whatever has been ATTACHed — so any value other than main emitted SQL against a database that never existed, and the host died on the first envelope write with:

SQLite Error 1: 'no such table: <name>.wolverine_incoming_envelopes'

The two halves had disagreed all along. Weasel's SqliteObjectName drops the schema from its qualified name, so the DDL had been creating a bare wolverine_incoming_envelopes while the inherited DML asked for a qualified one; the main default is the only thing that hid it.

The name is now folded into the table names as a prefix — a meaning SQLite can honour, giving several logically separate Wolverine table sets inside one database file:

opts.PersistMessagesWithSqlite(connectionString, "reporting");
// => reporting_wolverine_incoming_envelopes, reporting_wolverine_outgoing_envelopes, ...

This covers the envelope, node, control queue, tenant, listener and saga tables, plus the dead-letter index names, since SQLite shares one identifier namespace between tables and indexes.

No migration. main is the default and prefixes nothing, so every database provisioned before this release keeps its existing wolverine_* names. Only hosts that explicitly set a non-main name see different table names — and those hosts could not start at all before this fix. Postgres, SQL Server, MySQL and Oracle render exactly as before.

FisherIntegration.TransportSchemaName is now documented as what it has always been on a Fisher host: inert. Tracked in #3947.

Polecat unwraps `Nullable<T>` when determining an aggregate's id type

(#3948, closes #3942) Marten and Polecat disagreed for an aggregate whose id property is nullable: Polecat answered Nullable<T> verbatim, which is not a primitive id type, so the documented IdentifiedBy<T> escape hatch was skipped entirely. The two stores now agree.

Dependencies

Fisher 0.7.0 (#3946) — the package floor moves from 0.6.0 to 0.7.0. Note that Fisher 0.7.0 bundles JasperFx.Events.SourceGenerator inside its own nupkg, as Polecat already does. A project that also references that generator explicitly will get two analyzer instances and a CS0433 duplicate-type error until one copy is removed.

Full changelog: JasperFx/wolverine@V6.28.0...V6.28.1

6.28.0

Storage agnostic conventions wave: write handlers and HTTP endpoints that read and append without naming a store.

Highlights

Storage.AppendEvents() / Storage.StartStream() (#3934) — event stream counterparts to Storage.Store(), expressed entirely against JasperFx.Events.IEventOperations, so the same handler is valid on Marten, Polecat or Fisher with no IDocumentSession.
[FirstOrDefault] (#3933) — the singleton document [Entity] cannot express, since it has no identity to look up by.
[All] and [Queryable] (#3936) — every document of a type as an IReadOnlyList<T>, and a raw IQueryable<T> escape hatch.
Batched reads (#3938) — on Marten, Polecat and Fisher, two or more batchable reads in the same handler now resolve in a single database round trip. Nothing to turn on.
OnMissing.EmptyContentWith204, [NoContentIfMissing] / [NotFoundIfMissing] (#3931) — answer an empty 204 instead of a 404 when there is simply nothing to return.
DateTime / DateTimeOffset now in Wolverine.HTTP (#3932) — matches the long standing message handler convention. Previously such a parameter silently bound from the query string and arrived as default.

Notable fix

An IEventStoreOperations / IEventOperations handler or endpoint parameter now resolves and commits (#3936). CanApply recognized no event operations type, so AutoApplyTransactions skipped those chains and appended events were queued into the session's unit of work and never committed — with no exception thrown. This also affected each store's own event operations types, so it predates this release.

Also: [All] / [Queryable] / [FirstOrDefault] provider errors now name the declaring method (#3937).

Full detail in CHANGELOG.md.

6.27.1 Wolverine 6.27.1

A same-day patch on 6.27.0, fixing a regression that release introduced and closing the asymmetry that surfaced it.

Regression fix: `[WriteAggregate]` lost its not-found guard in 6.27.0

WriteAggregateAttribute derives from WriteModelAttribute and overrides neither Modify nor Required, so it inherited 6.27.0's nullability inference (GH-3916) wholesale. [WriteAggregate] shipped a year before that inference, so in 6.27.0 an existing handler like:

public static Events Handle(RecordDeposit command, [WriteAggregate] Account? account)

silently lost its not-found guard and began running against a model that was never loaded — for a write model, that means appending events against a stream that was not fetched.

[WriteAggregate] and [ReadAggregate] now pin the unconditional Required = true they have always had, in Marten, Polecat and Fisher alike. Say Required = false explicitly, or move to [WriteModel] / [ReadModel], to opt out.

If you are on 6.27.0 and use [WriteAggregate] with a nullable parameter and no explicit Required, upgrade.

`[ReadModel]` takes `Required` from the parameter's nullable annotation (#3929)

Matching what GH-3916 did for [WriteModel]: Order order is required and gets a not-found guard, Order? order is not and is handed to your method as null so your own null branch runs. An explicit Required at the call site still wins over the annotation.

This closes the write/read asymmetry — a handler moving between the two forms no longer needs a different attribute spelling for identical intent.

What deliberately did not change

[Entity] keeps its unconditional Required = true. It is the oldest and most widely used of these attributes and is heavily used in HTTP endpoints, where Required = true with OnMissing.Simple404 is the documented 404 behaviour. Loosening it would turn a clean 404 into a runtime NullReferenceException in an endpoint body.
[DeciderFunction] and [DcbModel] keep Required = false. Their model is folded out of an event stream or boundary and is always materialized, so absence is not the normal case; inferring here would tighten the default and could stop messages that process today.

Worth knowing

In an assembly compiled with <Nullable>disable</Nullable> a reference-type parameter reads as unknown rather than nullable, so [WriteModel] and [ReadModel] fall back to Required = true. The inference is a no-op for those projects rather than a silent behaviour change. Now documented in the persistence guide.

6.27.0 Wolverine 6.27.0

New: `WolverineFx.Fisher`

Fisher — the embedded SQLite document database and event store — is now a first-class Wolverine persistence integration, alongside Marten and Polecat.

builder.Services.AddFisher(opts => opts.Connection("Data Source=app.db"))
    .ApplyAllDatabaseChangesOnStartup()
    .IntegrateWithWolverine();

A Fisher-backed service is zero-infrastructure: no server, no container, no network. The transactional inbox/outbox, saga storage and the full aggregate handler workflow all work, and the store-agnostic [WriteModel] / [ReadModel] / [DeciderFunction] / [DcbModel] attributes run against it unchanged — the same handler code compiles and runs on any of the three stores.

Two SQLite realities shape it, both documented:

One writer per file. Wolverine's durability tables commit on Fisher's own connection inside Fisher's transaction. A second connection to the same file is a second writer and presents as a hang rather than an error.
DurabilityMode.Solo. Leader election and agent distribution need several nodes sharing one database; a Fisher store is a file.

Ancillary stores work too. AddFisherStore<T>().IntegrateWithWolverine() is supported, and [Storage(typeof(IMyStore))] routes a handler to it without naming Fisher in the consumer's source.

Not in this first release, each for a reason rather than for lack of time: multi-tenancy (Fisher's tenancy is a file per tenant), cluster durability modes, and transport schema stamping (SQLite has no schemas). See Fisher Integration.

Requires Fisher 0.6.0.

New: `[DcbModel]` — Dynamic Consistency Boundaries, store-agnostic

The DCB workflow joins the store-agnostic vocabulary in Wolverine core. Where [WriteModel] is about one stream, [DcbModel] spans every stream whose events match a tag query, with the store asserting at commit that no matching event landed in the meantime.

public static EventTagQuery Load(ReserveSeat command)
    => EventTagQuery.For(command.ScreeningId).Or(command.CustomerId);

public static SeatReserved Handle(ReserveSeat command, [DcbModel] SeatAvailability availability)
    => new(command.ScreeningId, command.CustomerId);

Wolverine.Marten.BoundaryModelAttribute and Wolverine.Polecat.BoundaryModelAttribute now inherit from it and behave identically — existing [BoundaryModel] code needs no change. Prefer [DcbModel] in new code.

`[WriteModel]` fixes

Required now defaults from the parameter's nullable annotation (#3916). Order order is required and gets a not-found guard; Order? order is not, and is handed to your method as null so your own null branch runs. A nullable annotation with Required = true was a contradiction that silently resolved in favour of the attribute default, making the handler's null branch dead code. Setting Required explicitly still overrides the annotation either way.

⚠️ Behaviour change for a handler with a nullable model parameter that relied on the implicit guard. Set Required = true explicitly to keep it.
[Identity] is now honoured (#3918). [DeciderFunction] always respected [Identity] on the command member; [WriteModel] did not, so the same command against the same model needed an explicit [WriteModel("...")] under one form and nothing under the other. Resolution order is now: explicit [WriteModel("orderId")], then [Identity], then {Model}Id, then id, then a strong typed id match.

Amazon SQS: oversized messages (#3926)

A message too big for SQS is no longer retried forever. SQS caps a message at 256KB and rejects a larger one with InvalidParameterValue - Message must be shorter than 262144 bytes (SenderFault: true). SenderFault: true means the identical request will fail identically forever, but Wolverine treated it as a transient send failure and re-queued it — which is why this presented as a flood of identical errors rather than one. An oversized message is now logged once and discarded.
... (truncated)

6.26.0 Upgrade note

This release moves the Critter Stack dependencies forward together:

package	from	to
JasperFx, JasperFx.Events (+ both source generators)	2.46.0	2.47.0
Marten, Marten.AspNetCore, Marten.Newtonsoft	9.22.6	9.23.0
Polecat	`[5.7.0,6.0.0)` (resolving to 5.7.0)	`[5.12.0,6.0.0)`

Polecat users get the larger jump of the two: the old range pin resolved to its 5.7.0 floor, so this is 5.7.0 → 5.12.0 in practice.

If you reference JasperFx.Events.SourceGenerator explicitly and reference Polecat, you may hit CS0433 ("the type <X>Evolver exists in both <YourAssembly> and <YourAssembly>"). The generator ships both bundled inside the Polecat nupkg and as a standalone package; when the two copies are the same version they load as two analyzer instances and each emits every projection's Evolver dispatcher. Polecat 5.12.0 bundles 2.47.0, which is what this release pins, so the pair now matches. The fix is to drop one instance — see PolecatTests.csproj for the DropDuplicateBundledEventSourceGenerator target we use, which keeps the explicitly-pinned generator and removes the bundled duplicate.

Two new packages

WolverineFx.DataAnnotationsValidation and WolverineFx.FluentValidation.Grpc are published for the first time in this release. Both were documented as installable but had never actually shipped — every version returned BlobNotFound from nuget.org — because each declared a PackageId while being absent from the packaging list. If you followed the Data Annotations validation or gRPC error details docs and found the package missing, it exists now. A build-time check keeps the two lists from drifting apart again. (#3905, #3909)

Fixes

A [WriteAggregate]-only chain now reports IsTransactional correctly. The Marten and Polecat aggregate handler workflows appended a SaveChangesAsync postprocessor but never set IChain.IsTransactional, so a chain reported having no transactional middleware while its generated code committed. The disagreement was visible to IHttpPolicy authors, who had no reliable signal for whether a chain would commit — the workaround was an unused IDocumentSession parameter on every such endpoint, purely to flip the detection. Thanks to @esond for the report and the fix. (#3893, #3901)

Outgoing batches no longer serialize eagerly. OutgoingMessageBatch built its contiguous byte[] in its constructor whether or not anything read it. (#3906)

Aggregate handler workflow unification (#3907, increment one)

Wolverine has carried two near-identical copies of the aggregate handler workflow — one in Wolverine.Marten, one in Wolverine.Polecat — and improvements had been landing on one copy at a time. This release starts implementing it once, in core.

Nothing is retired and no public API changes. [WriteAggregate], [ReadAggregate], [AggregateHandler], [ConsistentAggregate], Events, MartenOps/PolecatOps and the rest of each integration's surface stay exactly where they are.

What landed:

The drift between the two copies is reconciled, taking whichever side was correct rather than merging mechanically. The substantive one: AggregateHandling.DetermineVersionMember now returns MemberInfo? — Marten's copy used a null-forgiving operator that was masking a real null from IAggregateVersioning.VersionMember. Polecat regains AOT annotations it had dropped. Two reflectively-closed codegen frames widen a class constraint to notnull, matching IEventStream<T>'s own declaration; the narrower form threw for a struct aggregate instead of generating the same correct code.
IEventSourcingFrameProvider, the store seam — deliberately a sibling of IPersistenceFrameProvider rather than new members on it, so stores without event sourcing never grow no-op aggregate members.
The first shared mechanism moved into Wolverine.Persistence.EventSourcing: the event-capture frames and DetermineEventCaptureHandling, all written purely against JasperFx.Events' IEventStream<T>.
A reflection test enforcing that no core type shares a simple name with a public type in a Wolverine.<Store> integration, so a CS0104 ambiguity for users is caught by a failing test instead.

The bulk extraction continues in #3911. Also in this release: #3908, which pins what [Storage(typeof(...))] actually promises against a Marten ancillary store.

Upstream halves of this work: JasperFx/jasperfx#648, JasperFx/marten#5221, JasperFx/polecat#453.

6.25.5

6.25.5 supersedes the never-published 6.25.4 (its tag and release were retired), so the first two fixes below make their first NuGet appearance here.

Fixes

PostgreSQL dead-letter and outgoing counts are exact for small tables (GH-3885)

The PostgreSQL message-store counts for the dead-letter and outgoing tables now report exact numbers for small tables instead of the estimate that could read as zero right after activity. First staged for 6.25.4; this is its first published release.

The durable inbox routes by endpoint for sticky handlers (GH-3886)

Durable inbox recovery now routes each envelope by its owning endpoint, so sticky-handler ([StickyHandler] / endpoint-scoped) messages recovered from the inbox execute on the endpoint they were received on rather than falling back to the default route. Also first staged for 6.25.4.

Never export empty metrics snapshots + idle-tenant eviction (#3891)

Wolverine no longer exports metrics snapshots that contain no data, and per-tenant metric state for tenants that have gone idle is evicted after a configurable number of cycles via WolverineOptions.Metrics.TenantIdleEvictionCycles. This is the upstream half of CritterWatch#963 — at very high tenant counts, idle tenants no longer pin memory or pad every export.

Agents that exhaust node-local auto-restarts are released to a capable peer (GH-3888, #3896)

When a stalled agent uses up its node-local auto-restart budget, the node now releases the agent so a capable peer can pick it up, instead of retrying forever on the same node. A capability embargo prevents the agent from bouncing straight back to the node that just failed it.

Short-circuiting Before + Finally middleware no longer NREs (GH-3892, #3895)

Middleware that combines a short-circuiting Before method with a Finally method no longer produces a NullReferenceException at codegen time — and Finally now runs on the short-circuit path, as the middleware contract promises.

Saga diagnostics tolerate an unprovisioned saga table (GH-3887, #3894)

DatabaseSagaStoreDiagnostics.ReadSagaAsync / ListSagaInstancesAsync treat a missing saga table (Postgres 42P01 / SQL Server 208) as null / empty rather than surfacing a raw undefined-table error. A declared-but-never-persisted saga is a legitimate state, since AddSagaType is optional.

Polecat `TransportSchemaName` is honored (GH-3884, #3897)

PolecatIntegration.TransportSchemaName is now actually applied — previously the setting was inert and the transport tables always landed in the default schema.

Improvements

The stalled-agent auto-restart path is testable (#3890)

The auto-restart path now runs on TimeProvider, making it deterministic under test — with coverage added. Thanks @erdtsieck!

Message types can be exempted from partitioned processing (GH-3899, #3902)

MessagePartitioning.ExemptFromPartitionedProcessing<T>() exempts a message type from partitioned (GroupId-keyed) processing — exempt types ride the endpoint's normal parallelism while partitioned types keep strict per-group ordering.

Batched members' `DeliverBy` expiry is enforced again (GH-3898, #3903)

Expired members are shed at batch assembly with the normal discard observability, and a whole-batch backstop expires batches whose every member has lapsed.

The sharded execution block deserializes in parallel with ordered emission (GH-3900, #3904)

The sharded execution block's decompress/deserialize stage now runs N-wide while preserving per-group FIFO byte-for-byte.

... (truncated)

6.25.3

A silent data-plane bug for anyone combining Marten with a database-backed transport. Found from a user's minimal reproduction against CritterWatch.

What's Changed

GH-3883: the Marten integration no longer clobbers an explicit transport schema by @jeremydmiller in JasperFx/wolverine@694bf51f7

IntegrateWithWolverine() registers MartenIntegration as an IWolverineExtension, so its Configure() runs at host build — after an inline UsePostgresqlPersistenceAndTransport(..., transportSchema: ...) in the same options lambda. It then stamped its own schema names onto the shared PostgreSQL transport unconditionally, so the integration's defaults silently overwrote whatever the caller asked for.

The failure lands on the data plane rather than at startup, which is what makes it expensive to diagnose. A host without Marten honours the configured schema and publishes to {configured}.wolverine_queue_x; a Marten-backed consumer listens on wolverine_queues.wolverine_queue_x. Auto-provision creates both tables happily, nothing is logged on either side, and no message is ever delivered — the publisher's rows just accumulate in a table nobody polls:

 myapp_queues     | wolverine_queue_orders   <- publishers write here
 wolverine_queues | wolverine_queue_orders   <- the Marten-backed host listens here

TransportSchemaName now records whether it was explicitly assigned and is stamped onto the transport only then; MessageStorageSchemaName is stamped only when non-empty. Both currently-working cases are unchanged — an explicitly-set Marten knob still wins, and a host that configures neither still lands on wolverine_queues.

If you have been running Marten alongside UsePostgresqlPersistenceAndTransport with a custom transportSchema, check for a duplicate wolverine_queue_* table under wolverine_queues — that is undelivered mail, and it becomes reachable once you upgrade.

Known related gap

PolecatIntegration.TransportSchemaName is declared and documented but never applied — the mirror-image problem (inert rather than over-eager), so an explicit value there is silently ignored. Its sibling MessageStorageSchemaName is wired correctly. Tracked as #3884, not addressed in this release.

Full Changelog: JasperFx/wolverine@V6.25.2...V6.25.3

6.25.2

All related to CritterWatch

What's Changed

GH-3882: opt-in Buffered mode for global partitioned topology slots by @jeremydmiller in JasperFx/wolverine@5ef50f8ab

GlobalPartitionedMessageTopology.SetExternalTopology force-set EndpointMode.Durable on every external slot and companion local queue after the user's configure callback ran, with no way to opt out. For lossy, re-reported traffic — telemetry being the motivating case — that store-and-forwards every envelope through the application's own message store.

opts.MessagePartitioning.GlobalPartitioned(topology =>
{
    topology.UseShardedRabbitQueues("telemetry", 5);
    topology.Mode(EndpointMode.BufferedInMemory); // new — default stays Durable
});

The mode applies to the external slots and their companion local queues, and is order-independent (it may be set before or after the transport-specific UseSharded*Queues call). EndpointMode.Inline is rejected — partitioned slots depend on the external-listener-to-companion-queue bridge that inline endpoints bypass.

Full Changelog: JasperFx/wolverine@V6.25.1...V6.25.2

6.25.1

All related to CritterWatch

What's Changed

#3877: make agent distribution aware of cross-family node load by @jeremydmiller in #3877: make agent distribution aware of cross-family node load JasperFx/wolverine#3879
#3878: pin and document that blanket durability policies skip system endpoints by @jeremydmiller in #3878: pin and document that blanket durability policies skip system endpoints JasperFx/wolverine#3880

Full Changelog: JasperFx/wolverine@V6.25.0...V6.25.1

6.25.0

Couple bugs, one new API meant for CritterWatch

What's Changed

#3867 a batched handler participates in partitioned sequential processing by @jeremydmiller in #3867 a batched handler participates in partitioned sequential processing JasperFx/wolverine#3868
#3869: latch endpoint-originated causation reporting by @jeremydmiller in #3869: latch endpoint-originated causation reporting JasperFx/wolverine#3872
GlobalPartitionedMessageTopology.Except() (#3867 follow-up) by @jeremydmiller in GlobalPartitionedMessageTopology.Except<T>() (#3867 follow-up) JasperFx/wolverine#3873
#3871: apply endpoint policies to broker system endpoints by @jeremydmiller in #3871: apply endpoint policies to broker system endpoints JasperFx/wolverine#3874
#3870: route the durable inbox to a handler's enrolled DbContext store by @jeremydmiller in #3870: route the durable inbox to a handler's enrolled DbContext store JasperFx/wolverine#3875
#3871 follow-up: narrow the system endpoint compile to Rabbit MQ by @jeremydmiller in #3871 follow-up: narrow the system endpoint compile to Rabbit MQ JasperFx/wolverine#3876

Full Changelog: JasperFx/wolverine@V6.24.10...V6.25.0

6.24.10

Small bug fix release: queue endpoints addressed only by Uri on the database-backed transports (SQL Server, PostgreSQL, SQLite, MySQL) now sanitize the queue name the same way the fluent API does, so a name like sqlserver://my-service-control no longer produces invalid wolverine_queue_* table DDL from the dash. This was uncovered by CritterWatch's systemControlUri usage in the field.

What's Changed

Database queue Uris sanitize the queue name like the fluent API does by @jeremydmiller in Database queue Uris sanitize the queue name like the fluent API does JasperFx/wolverine#3865

Full Changelog: JasperFx/wolverine@V6.24.9...V6.24.10

6.24.9

This is mostly about CritterWatch uncovered issues with very high volumes of messaging via SQS and making the back pressure detection a bit more sophisticated

What's Changed

Batching pipelines: back-pressure sees their depth, faulted receivers rebuild, OOM can't fault the block (CritterWatch#942) by @jeremydmiller in Batching pipelines: back-pressure sees their depth, faulted receivers rebuild, OOM can't fault the block (CritterWatch#942) JasperFx/wolverine#3864

Full Changelog: JasperFx/wolverine@V6.24.8...V6.24.9

6.24.8

Bug fix release. Four durability and multi-tenancy fixes, all with regression coverage.

Fixes

#3856 — Dormant inbox rows for a durable local queue were never recovered (#3857)
PublishToPartitionedLocalMessaging() marks every slot ListenerScope.Exclusive, and the GH-3590 carve-out then handed inbox recovery to a loop that is never constructed for a local queue — a local queue never gets a ListeningAgent at all. Envelopes sat at status='Incoming', owner_id=0 indefinitely, surviving rolling deploys. Both guards implementing that hand-off now ask a single Endpoint.IsSingleNodeListener predicate, which LocalQueue answers false. Reported by @erdtsieck.

#3815 — forEveryDatabase visited the main database twice (#3858)
MultiTenantedMessageStore.ActiveDatabases() yields Main first, so on any multi-tenanted configuration the Oracle, PostgreSQL and MySQL queues counted the main database twice — GetAttributesAsync() reported a queue depth of 2 for a single row. Schema checks and purges also ran twice. SqlServer and Sqlite were already correct.

#3859 — MySQL multi-tenanted queues shared one physical table (#3861)
A MySQL schema is a database, so the single TransportSchemaName resolved every tenant to the same queue table: no isolation, and counts that multiplied by the tenant count instead of summing. Queue tables now resolve inside each tenant's own database. Single-database hosts are unaffected.

#3860 — MySQL database-per-tenant storage had no isolation (#3862)
The same root cause in the message stores: every tenant store received the one configured schema name, so inbox, outbox, dead letter, node and saga tables were shared across all tenants. Each tenant's database is now its own schema.

Upgrading

MySQL database-per-tenant users only. Before this release your tenant envelope rows all lived in the single configured schema. After upgrading, each tenant reads from its own database instead — drain or copy across any in-flight envelopes still sitting in the old shared tables before you upgrade. No other provider or configuration is affected.

Full changelog: JasperFx/wolverine@V6.24.7...V6.24.8

6.24.7

This is a fix release. Its centre of gravity is agent assignment: a leader that re-decided the same placements every cycle, and — hidden underneath that churn — a serial stop path that made every rebalance far slower th...

_Descri...

Description has been truncated

Bumps AWSSDK.S3 from 4.0.16 to 4.0.102.1 Bumps dotnet-coverage from 18.9.0 to 18.10.0 Bumps dotnet-ef from 10.0.10 to 10.0.11 Bumps Microsoft.AspNetCore.Authentication.JwtBearer from 10.0.10 to 10.0.11 Bumps Microsoft.AspNetCore.OpenApi from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.Configuration from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.Configuration.EnvironmentVariables from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.Configuration.UserSecrets from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.DependencyInjection.Abstractions from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.Logging.Abstractions from 10.0.10 to 10.0.11 Bumps Microsoft.Extensions.Options.ConfigurationExtensions from 10.0.10 to 10.0.11 Bumps Microsoft.NET.Test.Sdk from 18.7.0 to 18.9.0 Bumps Microsoft.Testing.Extensions.CodeCoverage from 18.9.0 to 18.10.0 Bumps NSubstitute from 6.0.0 to 6.2.0 Bumps Roslynator.Analyzers from 4.15.0 to 4.16.1 Bumps Scalar.AspNetCore from 2.16.16 to 2.16.20 Bumps SonarAnalyzer.CSharp from 10.31.0.145097 to 10.32.0.713 Bumps Testcontainers.Minio from 4.13.0 to 4.14.0 Bumps Testcontainers.PostgreSql from 4.13.0 to 4.14.0 Bumps Testcontainers.Redis from 4.13.0 to 4.14.0 Bumps WolverineFx from 6.22.0 to 6.29.0 Bumps WolverineFx.EntityFrameworkCore from 6.22.0 to 6.29.0 Bumps WolverineFx.Postgresql from 6.22.0 to 6.29.0 Bumps WolverineFx.RuntimeCompilation from 6.22.0 to 6.29.0 --- updated-dependencies: - dependency-name: AWSSDK.S3 dependency-version: 4.0.102.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: dotnet-coverage dependency-version: 18.10.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: dotnet-ef dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.AspNetCore.Authentication.JwtBearer dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.AspNetCore.OpenApi dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.Caching.StackExchangeRedis dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.Configuration dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.Configuration.EnvironmentVariables dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.Configuration.UserSecrets dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.Logging.Abstractions dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Extensions.Options.ConfigurationExtensions dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: Microsoft.Testing.Extensions.CodeCoverage dependency-version: 18.10.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: NSubstitute dependency-version: 6.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: Roslynator.Analyzers dependency-version: 4.16.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: Scalar.AspNetCore dependency-version: 2.16.20 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: SonarAnalyzer.CSharp dependency-version: 10.32.0.713 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: Testcontainers.Minio dependency-version: 4.14.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: Testcontainers.PostgreSql dependency-version: 4.14.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: Testcontainers.Redis dependency-version: 4.14.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx dependency-version: 6.29.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 6.29.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.Postgresql dependency-version: 6.29.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.29.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot · 2026-08-25T09:18:25Z

Looks like these dependencies are updatable in another way, so this is no longer needed.

dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Aug 18, 2026

dependabot Bot requested a review from tthanhtung92 as a code owner August 18, 2026 09:15

dependabot Bot added dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code labels Aug 18, 2026

dependabot Bot closed this Aug 25, 2026

dependabot Bot deleted the dependabot/nuget/dot-config/nuget-minor-and-patch-143ab32f92 branch August 25, 2026 09:18

Navigation Menu

Bump the nuget-minor-and-patch group with 25 updates - #15

Bump the nuget-minor-and-patch group with 25 updates#15
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/dot-config/nuget-minor-and-patch-143ab32f92

dependabot Bot commented on behalf of github Aug 18, 2026 •

edited

Loading

Uh oh!

dependabot Bot commented on behalf of github Aug 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Aug 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

18.9.0

What's Changed

New Contributors

18.8.1

What's Changed

18.8.0

What's Changed

6.2.0

NSubstitute v6.2.0

What's Changed

6.1.0

NSubstitute v6.1.0

What's Changed

New Contributors

4.16.1

Fixed

4.16.0

Added

Fixed

10.32.0.713

Release notes - .NET Analyzers - 10.32

Feature

False Positive

4.14.0

What's Changed

🚀 Features

🐛 Bug Fixes

🧹 Housekeeping

📦 Dependency Updates

4.14.0

What's Changed

🚀 Features

🐛 Bug Fixes

🧹 Housekeeping

📦 Dependency Updates

4.14.0

What's Changed

🚀 Features

🐛 Bug Fixes

🧹 Housekeeping

📦 Dependency Updates

6.29.0

AfterCommit — run work after the transactional commit

A store-agnostic EventsToAppend return type

Ask what will be handled, and how a batch is shaped

Durability agents no longer assigned to nodes that cannot run them

Ancillary store transaction ownership

RabbitMQ

Idle reaper no longer latches durable endpoints

6.28.1

New package

Fixes

A SQLite "schema name" is now the table name prefix it was documented to be

Polecat unwraps Nullable<T> when determining an aggregate's id type

Dependencies

6.28.0

Highlights

Notable fix

6.27.1

Wolverine 6.27.1

Regression fix: [WriteAggregate] lost its not-found guard in 6.27.0

[ReadModel] takes Required from the parameter's nullable annotation (#​3929)

What deliberately did not change

Worth knowing

6.27.0

Wolverine 6.27.0

New: WolverineFx.Fisher

New: [DcbModel] — Dynamic Consistency Boundaries, store-agnostic

[WriteModel] fixes

Amazon SQS: oversized messages (#​3926)

6.26.0

Upgrade note

Two new packages

Fixes

Aggregate handler workflow unification (#​3907, increment one)

6.25.5

Fixes

dependabot Bot commented on behalf of github Aug 18, 2026 •

edited

Loading

`AfterCommit` — run work after the transactional commit

A store-agnostic `EventsToAppend` return type

Polecat unwraps `Nullable<T>` when determining an aggregate's id type

Regression fix: `[WriteAggregate]` lost its not-found guard in 6.27.0

`[ReadModel]` takes `Required` from the parameter's nullable annotation (#3929)

New: `WolverineFx.Fisher`

New: `[DcbModel]` — Dynamic Consistency Boundaries, store-agnostic

`[WriteModel]` fixes

Amazon SQS: oversized messages (#3926)

Aggregate handler workflow unification (#3907, increment one)

Never export empty metrics snapshots + idle-tenant eviction (#3891)

Agents that exhaust node-local auto-restarts are released to a capable peer (GH-3888, #3896)

Short-circuiting Before + Finally middleware no longer NREs (GH-3892, #3895)

Saga diagnostics tolerate an unprovisioned saga table (GH-3887, #3894)

Polecat `TransportSchemaName` is honored (GH-3884, #3897)

The stalled-agent auto-restart path is testable (#3890)

Message types can be exempted from partitioned processing (GH-3899, #3902)

Batched members' `DeliverBy` expiry is enforced again (GH-3898, #3903)

The sharded execution block deserializes in parallel with ordered emission (GH-3900, #3904)