Bump the wolverine group with 5 updates#20
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps WolverineFx from 6.2.2 to 6.17.1 Bumps WolverineFx.EntityFrameworkCore from 6.2.2 to 6.17.1 Bumps WolverineFx.FluentValidation from 6.2.2 to 6.17.1 Bumps WolverineFx.Postgresql from 6.2.2 to 6.17.1 Bumps WolverineFx.RuntimeCompilation from 6.15.0 to 6.17.1 --- updated-dependencies: - dependency-name: WolverineFx dependency-version: 6.17.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: wolverine - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 6.17.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: wolverine - dependency-name: WolverineFx.FluentValidation dependency-version: 6.17.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: wolverine - dependency-name: WolverineFx.Postgresql dependency-version: 6.17.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: wolverine - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.17.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: wolverine ... Signed-off-by: dependabot[bot] <support@github.com>
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated WolverineFx from 6.2.2 to 6.17.1.
Release notes
Sourced from WolverineFx's releases.
6.17.1
Wolverine 6.17.1 is a bug-fix release covering EF Core outbox enlistment gaps in Wolverine.Http, persistence provider resolution, HTTP route parameter binding, multi-tenancy message store roles, and a RavenDB startup race. It also upgrades the Marten dependency to 9.14.1.
EF Core & persistence
DbContextand cascade messages only through a tuple return are now enlisted in the EF Core outbox, so cascaded messages are no longer sent before the transaction commits when usingLightweightmode (#3358, #3362)IStorageAction<T>/ storage side effects) are likewise enlisted in the EF Core outbox inLightweightmode (#3353, #3357)DbContext-based handlers get the correct transactional middleware (#3359, #3361)MessageStoreRole.Ancillaryis now honored for tenanted message stores (static tenants and master-table tenancy) instead of silently reportingMain(#3351), with the registration behavior now covered by tests across PostgreSQL, SQL Server, SQLite, MySQL, and OracleHTTP
[FromRoute(Name = "...")]is now honored on plain endpoint method parameters (previously only inside[AsParameters]types), enabling route segments like{journey-id}that aren't valid C# identifiers (#3356 — thanks to @outofrange-consulting!)RavenDB
Dependencies
Documentation
IDocumentSessionorDbContext), not the HTTP verb (#3355, #3360)6.17.0
Why is this such a big release? Because @jeremydmiller went on a 3 night vacation and the community decided to throw in issues and pull requests left and right!
A big theme was filling in the remaining gaps of "Name Broker" and "Broker per Tenant" support in every external messaging transport where it made sense to add that rather than just being Rabbit MQ, Azure Service Bus, and hit and miss everywhere else. We also added HTTP QUERY support.
What's Changed
... (truncated)
6.16.0
Lot of CritterWatch stuff, optimized SQL Server transport, new options for NServiceBus interop using SQL Server, bug fixes
What's Changed
Full Changelog: JasperFx/wolverine@V6.15.0...V6.16.0
6.15.0
Wolverine 6.15.0 aligns the critter-stack dependencies with the latest stable releases and brings observability, transport, and persistence improvements.
Dependency updates
GCP Pub/Sub
ListenOnlyAtLeader()) listeners now use a single shared subscription instead of a per-node subscription, restoring single-consumer semantics (#3258)Observability & health
BackgroundReceiveLoopwith receive-loop health reporting, adopted across SQS, Redis, PostgreSQL queue, SQL Server queue, and Kafka (#3236)EndpointHealthSnapshot;IReportConnectionStatefor NATS, MQTT, Pulsar, Redis (#3231)source(service name) (#3221); dimensional inbox/outbox/scheduled gauges (source + database); configurable millisecond histogram buckets (#3224)TagsonWolverineOptions, surfaced onServiceCapabilities(#3240)IGrpcEndpointManifest(#3235)Persistence & fixes
DbContext.Update()for untracked entities inStorage.Update(#3229)IEventStorefor Polecat stores so they're discoverable (#3219)NullMessageStorenever throws — no-ops every member for storeless observersPersistAgentRestrictionsAsyncno-ops on empty list (#3252);AssignmentGrid.ApplyRestrictionstolerates non-grid paused-agent URIsFull changelog: JasperFx/wolverine@V6.14.0...V6.15.0
6.14.0
The big ticket item is new interop options for Wolverine to/from MassTransit or NServiceBus using each's SQL Server or PostgreSQL queueing. Also quite a few Pulsar improvements. And community additions too!
What's Changed
Full Changelog: JasperFx/wolverine@V6.13.1...V6.14.0
6.13.1
Patch release on the 6.x line — a Critter Stack dependency refresh plus one targeted fix. No breaking changes.
🐛 Fixes
NULL received_at(#3165) — the dead-letter explorer could report 0 messages even when dead letters existed; the RDBMS DLQ readers now handle a nullreceived_atcolumn.⬆️ Dependencies
Full Changelog: JasperFx/wolverine@V6.13.0...V6.13.1
6.13.0
Wolverine 6.13.0 on the 6.0 line (JasperFx 2.x, net9.0/net10.0). The headline is a top-to-bottom Kafka integration re-evaluation (epic #3134) that makes the transport idiomatic and high-throughput, plus
[AsParameters]HTTP fidelity fixes and event-subscription/projection-distribution hardening. No breaking changes.🚀 Kafka integration re-evaluation (#3134)
CommitMode(#3152) —StoreThenAutoFlush(default, non-blocking idiomatic throughput),PerMessage, andCommitOffsetsAfterCount/AfterIntervalbatch modes.read_committedoffset gaps.AutoOffsetResetand ephemeral hot-tail / broadcast consume (#3155).Assign(#3156).read_committedisolation, with EOS guidance (#3157).OnException<T>().MoveToKafkaRetryTopic(...)DSL (#3160).ExtendConsumerConfigurationnow preserves parent/global consumer settings (#3151).🌐 HTTP —
[AsParameters](#3135)[FromBody]in[AsParameters]: binds null withrequired:false(#3142)[AsParameters]+[FromBody]+[WriteAggregate]codegen 500 (#3143/#3144)[AsParameters]as the idiomatic route/body split (#3145)🗄️ Event subscriptions, projections & distribution
🐛 Other fixes
Full Changelog: JasperFx/wolverine@V6.12.0...V6.13.0
6.12.0
What's Changed
Full Changelog: JasperFx/wolverine@V6.11.0...V6.12.0
6.11.0
The Polecat change was necessary for CritterWatch persistence with SQL Server. The inbox cleanup should help with very busy Wolverine systems be a bit easier on databases.
What's Changed
Full Changelog: JasperFx/wolverine@V6.10.0...V6.11.0
6.10.0
New Polecat integration for ancillary store support within Wolverine that folks doing modular monoliths will want -- and we needed in CritterWatch post haste. Also new options for configuring Redis.
What's Changed
Full Changelog: JasperFx/wolverine@V6.9.0...V6.10.0
6.9.0
This release was mostly about CritterWatch, but does have some new DLQ functionality, which was meant to complement CritterWatch. Couple bug fixes too though.
What's Changed
Full Changelog: JasperFx/wolverine@V6.8.0...V6.9.0
6.8.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.7.0...V6.8.0
6.7.0
What's Changed
Full Changelog: JasperFx/wolverine@V6.6.0...V6.7.0
6.6.0
What's Changed
IDeadLetterInterceptor: an exception-handling seam for durable dead letters by @mysticmind in AddIDeadLetterInterceptor: an exception-handling seam for durable dead letters JasperFx/wolverine#3046Full Changelog: JasperFx/wolverine@V6.5.1...V6.6.0
6.5.1
This is a super small change for CritterWatch testing.
What's Changed
Full Changelog: JasperFx/wolverine@V6.5.0...V6.5.1
6.5.0
One new API in the Kafka support, but mostly just some bug fixes and extra test coverage for the Marten integration
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.4.1...V6.5.0
6.4.1
Just hardening Wolverine against a condition that only happens (we think) in CritterWatch
What's Changed
Full Changelog: JasperFx/wolverine@V6.4.0...V6.4.1
6.4.0
This release was 100% about CritterWatch and does not impact any other functionality
What's Changed
Full Changelog: JasperFx/wolverine@V6.3.2...V6.4.0
6.3.2
What's Changed
Full Changelog: JasperFx/wolverine@V6.3.0...V6.3.2
6.3.0
The top line change here was a lot of work to make Wolverine able to pre-generate code as F# in addition to the existing C# model.
What's Changed
Full Changelog: JasperFx/wolverine@V6.2.2...V6.3.0
Commits viewable in compare view.
Updated WolverineFx.EntityFrameworkCore from 6.2.2 to 6.17.1.
Release notes
Sourced from WolverineFx.EntityFrameworkCore's releases.
6.17.1
Wolverine 6.17.1 is a bug-fix release covering EF Core outbox enlistment gaps in Wolverine.Http, persistence provider resolution, HTTP route parameter binding, multi-tenancy message store roles, and a RavenDB startup race. It also upgrades the Marten dependency to 9.14.1.
EF Core & persistence
DbContextand cascade messages only through a tuple return are now enlisted in the EF Core outbox, so cascaded messages are no longer sent before the transaction commits when usingLightweightmode (#3358, #3362)IStorageAction<T>/ storage side effects) are likewise enlisted in the EF Core outbox inLightweightmode (#3353, #3357)DbContext-based handlers get the correct transactional middleware (#3359, #3361)MessageStoreRole.Ancillaryis now honored for tenanted message stores (static tenants and master-table tenancy) instead of silently reportingMain(#3351), with the registration behavior now covered by tests across PostgreSQL, SQL Server, SQLite, MySQL, and OracleHTTP
[FromRoute(Name = "...")]is now honored on plain endpoint method parameters (previously only inside[AsParameters]types), enabling route segments like{journey-id}that aren't valid C# identifiers (#3356 — thanks to @outofrange-consulting!)RavenDB
Dependencies
Documentation
IDocumentSessionorDbContext), not the HTTP verb (#3355, #3360)6.17.0
Why is this such a big release? Because @jeremydmiller went on a 3 night vacation and the community decided to throw in issues and pull requests left and right!
A big theme was filling in the remaining gaps of "Name Broker" and "Broker per Tenant" support in every external messaging transport where it made sense to add that rather than just being Rabbit MQ, Azure Service Bus, and hit and miss everywhere else. We also added HTTP QUERY support.
What's Changed
... (truncated)
6.16.0
Lot of CritterWatch stuff, optimized SQL Server transport, new options for NServiceBus interop using SQL Server, bug fixes
What's Changed
Full Changelog: JasperFx/wolverine@V6.15.0...V6.16.0
6.15.0
Wolverine 6.15.0 aligns the critter-stack dependencies with the latest stable releases and brings observability, transport, and persistence improvements.
Dependency updates
GCP Pub/Sub
ListenOnlyAtLeader()) listeners now use a single shared subscription instead of a per-node subscription, restoring single-consumer semantics (#3258)Observability & health
BackgroundReceiveLoopwith receive-loop health reporting, adopted across SQS, Redis, PostgreSQL queue, SQL Server queue, and Kafka (#3236)EndpointHealthSnapshot;IReportConnectionStatefor NATS, MQTT, Pulsar, Redis (#3231)source(service name) (#3221); dimensional inbox/outbox/scheduled gauges (source + database); configurable millisecond histogram buckets (#3224)TagsonWolverineOptions, surfaced onServiceCapabilities(#3240)IGrpcEndpointManifest(#3235)Persistence & fixes
DbContext.Update()for untracked entities inStorage.Update(#3229)IEventStorefor Polecat stores so they're discoverable (#3219)NullMessageStorenever throws — no-ops every member for storeless observersPersistAgentRestrictionsAsyncno-ops on empty list (#3252);AssignmentGrid.ApplyRestrictionstolerates non-grid paused-agent URIsFull changelog: JasperFx/wolverine@V6.14.0...V6.15.0
6.14.0
The big ticket item is new interop options for Wolverine to/from MassTransit or NServiceBus using each's SQL Server or PostgreSQL queueing. Also quite a few Pulsar improvements. And community additions too!
What's Changed
Full Changelog: JasperFx/wolverine@V6.13.1...V6.14.0
6.13.1
Patch release on the 6.x line — a Critter Stack dependency refresh plus one targeted fix. No breaking changes.
🐛 Fixes
NULL received_at(#3165) — the dead-letter explorer could report 0 messages even when dead letters existed; the RDBMS DLQ readers now handle a nullreceived_atcolumn.⬆️ Dependencies
Full Changelog: JasperFx/wolverine@V6.13.0...V6.13.1
6.13.0
Wolverine 6.13.0 on the 6.0 line (JasperFx 2.x, net9.0/net10.0). The headline is a top-to-bottom Kafka integration re-evaluation (epic #3134) that makes the transport idiomatic and high-throughput, plus
[AsParameters]HTTP fidelity fixes and event-subscription/projection-distribution hardening. No breaking changes.🚀 Kafka integration re-evaluation (#3134)
CommitMode(#3152) —StoreThenAutoFlush(default, non-blocking idiomatic throughput),PerMessage, andCommitOffsetsAfterCount/AfterIntervalbatch modes.read_committedoffset gaps.AutoOffsetResetand ephemeral hot-tail / broadcast consume (#3155).Assign(#3156).read_committedisolation, with EOS guidance (#3157).OnException<T>().MoveToKafkaRetryTopic(...)DSL (#3160).ExtendConsumerConfigurationnow preserves parent/global consumer settings (#3151).🌐 HTTP —
[AsParameters](#3135)[FromBody]in[AsParameters]: binds null withrequired:false(#3142)[AsParameters]+[FromBody]+[WriteAggregate]codegen 500 (#3143/#3144)[AsParameters]as the idiomatic route/body split (#3145)🗄️ Event subscriptions, projections & distribution
🐛 Other fixes
Full Changelog: JasperFx/wolverine@V6.12.0...V6.13.0
6.12.0
What's Changed
Full Changelog: JasperFx/wolverine@V6.11.0...V6.12.0
6.11.0
The Polecat change was necessary for CritterWatch persistence with SQL Server. The inbox cleanup should help with very busy Wolverine systems be a bit easier on databases.
What's Changed
Full Changelog: JasperFx/wolverine@V6.10.0...V6.11.0
6.10.0
New Polecat integration for ancillary store support within Wolverine that folks doing modular monoliths will want -- and we needed in CritterWatch post haste. Also new options for configuring Redis.
What's Changed
Full Changelog: JasperFx/wolverine@V6.9.0...V6.10.0
6.9.0
This release was mostly about CritterWatch, but does have some new DLQ functionality, which was meant to complement CritterWatch. Couple bug fixes too though.
What's Changed
Full Changelog: JasperFx/wolverine@V6.8.0...V6.9.0
6.8.0
What's Changed
New Contributors
Full Changelog: JasperFx/wolverine@V6.7.0...V6.8.0
6.7.0
What's Changed
Full Changelog: JasperFx/wolverine@V6.6.0...V6.7.0
6.6.0
What's Changed
IDeadLetterInterceptor: an exception-handling seam for durable dead letters by @mysticmind in AddIDeadLetterInterceptor: an exception-handling seam for durable dead letters JasperFx/wolverine#3046_Desc...
Description has been truncated