Bump Marten and Marten.AspNetCore - #24
Conversation
Bumps Marten from 9.17.1 to 9.20.1 Bumps Marten.AspNetCore from 9.17.1 to 9.20.1 --- updated-dependencies: - dependency-name: Marten dependency-version: 9.20.1 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: Marten.AspNetCore dependency-version: 9.20.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
WolverineFx/.Http/.Marten/.RabbitMQ/.RuntimeCompilation to 6.23.1, Marten/ Marten.AspNetCore to 9.20.1 - applied as one manual bump instead of merging Dependabot PRs #24/#27/#28/#29/#30 individually, since those packages release in lockstep (per this file's own existing comment) and the 5 PRs disagreed with each other on shared version lines (#24 vs #28 both touched Marten to different targets; #27/#29/#30 all touched WolverineFx independently). Verified: solution builds clean, all 383 non-integration tests pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Superseded by e3f9593 — WolverineFx/.Http/.Marten/.RabbitMQ/.RuntimeCompilation and Marten/Marten.AspNetCore are consolidated into one manual bump instead of merging this PR individually, since these packages release in lockstep and several of these Dependabot PRs disagreed with each other on the same version lines (e.g. this PR vs #24/#28 both touching Marten to different targets, or #27/#29/#30 all touching WolverineFx independently). Verified: build clean, all 383 non-integration tests pass. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Updated Marten from 9.17.1 to 9.20.1.
Release notes
Sourced from Marten's releases.
9.20.1
Two real improvements:
What's Changed
Full Changelog: JasperFx/marten@V9.20.0...V9.20.1
9.20.0
Bug fixes around permutations of the natural key usage, new convenience mechanisms for querying for event store data
What's Changed
Full Changelog: JasperFx/marten@V9.19.0...V9.20.0
9.19.0
Marten 9.19.0 is a maintenance release adopting the coordinated JasperFx / JasperFx.Events 2.35.0 drop, with a new projection side-effect capability and a secondary-store fix.
Event sourcing
RaiseSideEffectsslice-identity overload — JasperFx.Events 2.35.0 (jasperfx#561) adds a backwards-compatible aggregation-projection overloadRaiseSideEffects(IDocumentOperations operations, TId id, IEventSlice<TDoc> slice). The newidparameter hands you the slice identity even whenslice.Snapshotis null because the aggregate was deleted in the same batch — so aMultiStreamProjectioncan recover the aggregate key to emit a follow-on event or publish a message on deletion. The original two-argument overload is unchanged, and the new one delegates to it by default. Documented with a compiled sample in Side Effects.Fixes
SecondaryStoreConfig.BuildthrewUriFormatExceptionwhen a secondary store was registered with a generic marker interface (e.g.AddMartenStore<IMartenStoreMarker<MyContext>>()). A closed generic CLR type name contains a backtick + arity, which is not a valid URI host. Themarten://subject is now sanitized (arity stripped, generic argument names folded in so distinct closed generics still map to distinct subjects).Dependencies
Notes
running_on_nodeunder managed distribution) is resolved on the Marten side and closed; the node-stamping half ships in the JasperFx 2.35.0 / Wolverine distribution layer.9.18.0
Marten 9.18.0 focuses on raw-JSON streaming endpoints for ASP.NET Core, server-side LINQ
Select()projection, and continued event-store observability work.ASP.NET Core streaming & pagination
StreamPaged<T>— stream a paged JSON envelope (pageNumber/pageSize/totalItemCount/pageCount/hasNextPage/hasPreviousPage/items) in a single round trip via acount(*) OVER()window column (#5014). Test coverage hardened to pin the camelCase wire contract, page-past-end behavior, and filtered totals (#5028).StreamPagedByCursor<T>— keyset ("seek") pagination that costs the same regardless of depth, using an opaque continuation cursor (#5016). Now streams the raw, already-persisteddatacolumn byte-identical toStreamMany/StreamPaged(no hydrate + re-serialize) by reading the next cursor's ORDER BY key values off the same reader; a malformed client-supplied cursor now returns a clean 400 instead of a 500 (#5033).If-None-Match(304) conditional-request support onStreamOne<T>andStreamAggregate<T>(#5015).StreamOne<T>now reads the document'smt_versioninline in the same single round trip (no follow-up metadata query), and thewhere T : notnullconstraint tightening was reversed (#5030).LINQ
Select()projections (x => new Dto { A = x.A, B = x.Nested.B }) now translate to a server-sidejsonb_build_object(...)expression that is streamable as raw JSON, instead of hydrating the full document and projecting on the client (#5017). Value-preserving conversions — widening numerics (int→long/decimal), boxing toobject, nullable wrapping,enum→integral underEnumStorage.AsInteger— stay translatable and streamable; only lossy/computed conversions fall back (#5032).Where()over events (#5004).AggregateToMany()LINQ operator — run an event query through a multi-stream projection (#5003).Event store, projections & daemon
extended_progression_batch_write(#5023);running_on_nodewrite-path regression coverage (#5001 / #5007). The cross-reporunning_on_nodepopulation under Wolverine-managed distribution is completed via JasperFx 2.34.0 + Wolverine.ReadStreamAsync/GetRecentStreamsAsyncoverrides honor tenancy (#5020, #5025), plus aMultiStreamProjectionstepthrough via the instrumented fold inEventStoreExplorer(#5002).ExternallyManageddaemon support (#4992).Multi-tenancy & infrastructure
Dependencies
Full changelog: JasperFx/marten@V9.17.0...V9.18.0
Commits viewable in compare view.
Updated Marten.AspNetCore from 9.17.1 to 9.20.1.
Release notes
Sourced from Marten.AspNetCore's releases.
9.20.1
Two real improvements:
What's Changed
Full Changelog: JasperFx/marten@V9.20.0...V9.20.1
9.20.0
Bug fixes around permutations of the natural key usage, new convenience mechanisms for querying for event store data
What's Changed
Full Changelog: JasperFx/marten@V9.19.0...V9.20.0
9.19.0
Marten 9.19.0 is a maintenance release adopting the coordinated JasperFx / JasperFx.Events 2.35.0 drop, with a new projection side-effect capability and a secondary-store fix.
Event sourcing
RaiseSideEffectsslice-identity overload — JasperFx.Events 2.35.0 (jasperfx#561) adds a backwards-compatible aggregation-projection overloadRaiseSideEffects(IDocumentOperations operations, TId id, IEventSlice<TDoc> slice). The newidparameter hands you the slice identity even whenslice.Snapshotis null because the aggregate was deleted in the same batch — so aMultiStreamProjectioncan recover the aggregate key to emit a follow-on event or publish a message on deletion. The original two-argument overload is unchanged, and the new one delegates to it by default. Documented with a compiled sample in Side Effects.Fixes
SecondaryStoreConfig.BuildthrewUriFormatExceptionwhen a secondary store was registered with a generic marker interface (e.g.AddMartenStore<IMartenStoreMarker<MyContext>>()). A closed generic CLR type name contains a backtick + arity, which is not a valid URI host. Themarten://subject is now sanitized (arity stripped, generic argument names folded in so distinct closed generics still map to distinct subjects).Dependencies
Notes
running_on_nodeunder managed distribution) is resolved on the Marten side and closed; the node-stamping half ships in the JasperFx 2.35.0 / Wolverine distribution layer.9.18.0
Marten 9.18.0 focuses on raw-JSON streaming endpoints for ASP.NET Core, server-side LINQ
Select()projection, and continued event-store observability work.ASP.NET Core streaming & pagination
StreamPaged<T>— stream a paged JSON envelope (pageNumber/pageSize/totalItemCount/pageCount/hasNextPage/hasPreviousPage/items) in a single round trip via acount(*) OVER()window column (#5014). Test coverage hardened to pin the camelCase wire contract, page-past-end behavior, and filtered totals (#5028).StreamPagedByCursor<T>— keyset ("seek") pagination that costs the same regardless of depth, using an opaque continuation cursor (#5016). Now streams the raw, already-persisteddatacolumn byte-identical toStreamMany/StreamPaged(no hydrate + re-serialize) by reading the next cursor's ORDER BY key values off the same reader; a malformed client-supplied cursor now returns a clean 400 instead of a 500 (#5033).If-None-Match(304) conditional-request support onStreamOne<T>andStreamAggregate<T>(#5015).StreamOne<T>now reads the document'smt_versioninline in the same single round trip (no follow-up metadata query), and thewhere T : notnullconstraint tightening was reversed (#5030).LINQ
Select()projections (x => new Dto { A = x.A, B = x.Nested.B }) now translate to a server-sidejsonb_build_object(...)expression that is streamable as raw JSON, instead of hydrating the full document and projecting on the client (#5017). Value-preserving conversions — widening numerics (int→long/decimal), boxing toobject, nullable wrapping,enum→integral underEnumStorage.AsInteger— stay translatable and streamable; only lossy/computed conversions fall back (#5032).Where()over events (#5004).AggregateToMany()LINQ operator — run an event query through a multi-stream projection (#5003).Event store, projections & daemon
extended_progression_batch_write(#5023);running_on_nodewrite-path regression coverage (#5001 / #5007). The cross-reporunning_on_nodepopulation under Wolverine-managed distribution is completed via JasperFx 2.34.0 + Wolverine.ReadStreamAsync/GetRecentStreamsAsyncoverrides honor tenancy (#5020, #5025), plus aMultiStreamProjectionstepthrough via the instrumented fold inEventStoreExplorer(#5002).ExternallyManageddaemon support (#4992).Multi-tenancy & infrastructure
Dependencies
Full changelog: JasperFx/marten@V9.17.0...V9.18.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)