Bump the critter-stack group with 5 updates#60
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps JasperFx.Events.SourceGenerator from 2.5.0 to 2.8.2 Bumps Marten from 9.3.5 to 9.6.0 Bumps Marten.AspNetCore from 9.3.5 to 9.6.0 Bumps WolverineFx.Marten from 6.3.2 to 6.5.1 Bumps WolverineFx.RuntimeCompilation from 6.3.2 to 6.5.1 --- updated-dependencies: - dependency-name: JasperFx.Events.SourceGenerator dependency-version: 2.8.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: critter-stack - dependency-name: Marten dependency-version: 9.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: critter-stack - dependency-name: Marten.AspNetCore dependency-version: 9.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: critter-stack - dependency-name: WolverineFx.Marten dependency-version: 6.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: critter-stack - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.5.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: critter-stack ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
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 JasperFx.Events.SourceGenerator from 2.5.0 to 2.8.2.
Release notes
Sourced from JasperFx.Events.SourceGenerator's releases.
2.8.1
What's Changed
Full Changelog: JasperFx/jasperfx@V2.5.0...V2.8.1
Commits viewable in compare view.
Updated Marten from 9.3.5 to 9.6.0.
Release notes
Sourced from Marten's releases.
9.6.0
There's a couple tenant aware APIs that are new, so this had to be a minor point bump. The majority of the work in this release was stress testing projection rebuilds and ensuring there was never any concurrent access of un-thread safe dictionaries inside of the async daemon that happened as a side effect of 9.0 changes.
What's Changed
Full Changelog: JasperFx/marten@V9.5.3...V9.6.0
9.5.3
This is a little optimization to the new 9.* code that eliminated the runtime codegen, and a fix for the daemon being a little vulnerable to concurrency in its internals -- which is also an optimization here.
What's Changed
Full Changelog: JasperFx/marten@9.5.2...V9.5.3
9.5.2
Bug fixes
mt_archive_streamemits explicit column lists in its INSERT…SELECT, survivingALTER TABLE ADD COLUMNmigrations that reorder the physical column layout (previously failed with42804after a column was added tomt_events).BulkInsertEventsAsyncwritesmt_streams.typefrom theStreamAction'sAggregateType, restoringUseMandatoryStreamTypeDeclarationsupport on the bulk path.AddMartenManagedTenantsAsyncno longer leaves a half-installed schema underAutoCreate.None. The admin call eagerly applies the events feature via a per-featureCreateMigrationAsync+ scopedCreateOrUpdateapply, so the next append succeeds end-to-end on a virgin schema (previously failed with42P01/42883).e.tenant_id = t.tenant_id, eliminating own-event duplication under per-tenant sequences withUseTenantPartitionedEvents.Test coverage
TenantPartitionedEventsTestsproject (~170 tests across 50 files) covering append / read / projections / admin / DCB / async daemon / regressions underUseTenantPartitionedEvents.FlatTableProjection), #4651 (DetermineActionAsync), #4652 (doc-tables-NOT-partitioned-by-default invariant).AutoCreate.CreateOnlycontinues to work via the lazy schema-apply path, by design (no SUT change needed).Known follow-up — NOT in this release
AddGlobalProjection × UseTenantPartitionedEventsfailsMT002because the global event decorator writes to the*DEFAULT*tenant slot, which can't be a Postgres partition suffix. Test pin is in master asserting the throw; the underlying fix requires either routing global-aggregate events through a sibling non-partitioned table or reserving a default-tenant partition suffix. Marked as an enhancement, deferred to a later release.🤖 Release notes assembled with Claude Code
9.5.1
What's Changed
Full Changelog: JasperFx/marten@V9.5.0...V9.5.1
9.5.0
The minor point bump here is because of some CritterWatch related features, otherwise this is all bug fixes
What's Changed
New Contributors
Full Changelog: JasperFx/marten@V9.4.0...V9.5.0
9.4.0
Marten 9.4.0
Per-tenant event partitioning and a tenant-aware async projection daemon (#4596 / CritterWatch#209). Built on JasperFx 2.5.0.
Highlights
opts.Events.UseTenantPartitionedEvents = true. On top of conjoined event tenancy, Marten partitionsmt_events/mt_streamsbytenant_id(native PostgreSQL LIST partitioning), gives each tenant its own event sequence (mt_events_sequence_{suffix}), and keysmt_event_progressionby(name, tenant_id). Removes the single shared event store as a scalability bottleneck across tenants.{Name}:Allshard.Constraints for per-tenant partitioning
Validated at
DocumentStoreconstruction:Events.TenancyStyle = TenancyStyle.Conjoined.EventAppendMode.Quick/QuickWithServerTimestamps);EventAppendMode.Richis out of scope.Events.UseArchivedStreamPartitioning(sub-partitioning by bothtenant_idandis_archivedis a planned follow-up).The flag defaults to
false; existing stores keep the global append path byte-for-byte.Dependencies
SubscriptionAgentoptimized-rebuild double-load fix).Documentation
Commits viewable in compare view.
Updated Marten.AspNetCore from 9.3.5 to 9.6.0.
Release notes
Sourced from Marten.AspNetCore's releases.
9.6.0
There's a couple tenant aware APIs that are new, so this had to be a minor point bump. The majority of the work in this release was stress testing projection rebuilds and ensuring there was never any concurrent access of un-thread safe dictionaries inside of the async daemon that happened as a side effect of 9.0 changes.
What's Changed
Full Changelog: JasperFx/marten@V9.5.3...V9.6.0
9.5.3
This is a little optimization to the new 9.* code that eliminated the runtime codegen, and a fix for the daemon being a little vulnerable to concurrency in its internals -- which is also an optimization here.
What's Changed
Full Changelog: JasperFx/marten@9.5.2...V9.5.3
9.5.2
Bug fixes
mt_archive_streamemits explicit column lists in its INSERT…SELECT, survivingALTER TABLE ADD COLUMNmigrations that reorder the physical column layout (previously failed with42804after a column was added tomt_events).BulkInsertEventsAsyncwritesmt_streams.typefrom theStreamAction'sAggregateType, restoringUseMandatoryStreamTypeDeclarationsupport on the bulk path.AddMartenManagedTenantsAsyncno longer leaves a half-installed schema underAutoCreate.None. The admin call eagerly applies the events feature via a per-featureCreateMigrationAsync+ scopedCreateOrUpdateapply, so the next append succeeds end-to-end on a virgin schema (previously failed with42P01/42883).e.tenant_id = t.tenant_id, eliminating own-event duplication under per-tenant sequences withUseTenantPartitionedEvents.Test coverage
TenantPartitionedEventsTestsproject (~170 tests across 50 files) covering append / read / projections / admin / DCB / async daemon / regressions underUseTenantPartitionedEvents.FlatTableProjection), #4651 (DetermineActionAsync), #4652 (doc-tables-NOT-partitioned-by-default invariant).AutoCreate.CreateOnlycontinues to work via the lazy schema-apply path, by design (no SUT change needed).Known follow-up — NOT in this release
AddGlobalProjection × UseTenantPartitionedEventsfailsMT002because the global event decorator writes to the*DEFAULT*tenant slot, which can't be a Postgres partition suffix. Test pin is in master asserting the throw; the underlying fix requires either routing global-aggregate events through a sibling non-partitioned table or reserving a default-tenant partition suffix. Marked as an enhancement, deferred to a later release.🤖 Release notes assembled with Claude Code
9.5.1
What's Changed
Full Changelog: JasperFx/marten@V9.5.0...V9.5.1
9.5.0
The minor point bump here is because of some CritterWatch related features, otherwise this is all bug fixes
What's Changed
New Contributors
Full Changelog: JasperFx/marten@V9.4.0...V9.5.0
9.4.0
Marten 9.4.0
Per-tenant event partitioning and a tenant-aware async projection daemon (#4596 / CritterWatch#209). Built on JasperFx 2.5.0.
Highlights
opts.Events.UseTenantPartitionedEvents = true. On top of conjoined event tenancy, Marten partitionsmt_events/mt_streamsbytenant_id(native PostgreSQL LIST partitioning), gives each tenant its own event sequence (mt_events_sequence_{suffix}), and keysmt_event_progressionby(name, tenant_id). Removes the single shared event store as a scalability bottleneck across tenants.{Name}:Allshard.Constraints for per-tenant partitioning
Validated at
DocumentStoreconstruction:Events.TenancyStyle = TenancyStyle.Conjoined.EventAppendMode.Quick/QuickWithServerTimestamps);EventAppendMode.Richis out of scope.Events.UseArchivedStreamPartitioning(sub-partitioning by bothtenant_idandis_archivedis a planned follow-up).The flag defaults to
false; existing stores keep the global append path byte-for-byte.Dependencies
SubscriptionAgentoptimized-rebuild double-load fix).Documentation
Commits viewable in compare view.
Updated WolverineFx.Marten from 6.3.2 to 6.5.1.
Release notes
Sourced from WolverineFx.Marten's releases.
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
Commits viewable in compare view.
Updated WolverineFx.RuntimeCompilation from 6.3.2 to 6.5.1.
Release notes
Sourced from WolverineFx.RuntimeCompilation's releases.
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
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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions