Bump EventFlow.Autofac from 0.72.3914 to 0.81.4483

[dependabot-preview]

Bumps EventFlow.Autofac from 0.72.3914 to 0.81.4483.

Release notes

Sourced from EventFlow.Autofac's releases.

v0.81.4483

• Breaking: Elasticsearch NEST Nuget Library updated from v6.1.0 to v7.8.2
• New: Now possible to implement error handlers for specific sagas using ISagaErrorHandler<TSaga>
• Fixed: You can now create Id : Identity<Id>

v0.80.4377

• Breaking: To support .NET going forward, all EventFlow test have been converted from .NET Framework 4.x to .NET Core 3.1. This however, introduced a set of breaking changes
  • EntityFramework has been updated from 2.2.6 to 3.1.5
  • IHangfireJobRunner.Execute is now IHangfireJobRunner.ExecuteAsync
• Breaking: Merged AggregateReadStoreManager and SingleAggregateReadStoreManager into one class in order to always guarantee in-order event processing
• Breaking: Marked the UseReadStoreFor<,,,> configuration methods as obsolete, in favor of the simpler overloads with less type parameters (as those automatically figure out the AggregateRoot and Id types and configure the more reliable SingleAggregateReadStoreManager implementation)
• Obsolete: The class AsyncHelper and all non-async methods using it have been marked obsolete and will be removed in EventFlow 1.0 (not planned yet). If you rely on these non-async methods, then merely copy-paste the AsyncHelper from the EventFlow code base and continue using it in your transition to async only
• Fixed: An issue where EntityFrameworkEventPersistence could possibly save aggregate events out of order, which would lead to out-of-order application when streaming events ordered by GlobalSequenceNumber
• New: FilesEventPersistence now uses relative paths
• New: A new set of hook-in interfaces are provided from this release, which should make it easier to implement crash resilience (#439) in EventFlow. Please note that this new API is experimentational and subject to change as different strategies are implemented
  • IAggregateStoreResilienceStrategy
  • IDispatchToReadStoresResilienceStrategy
  • IDispatchToSubscriberResilienceStrategy
  • ISagaUpdateResilienceStrategy

v0.79.4216

• New: Added .NET Core 3.1 target for the EventFlow and EventFlow.EntityFramework packages
• Added quoting to the SQL query generator for the column names

v0.78.4205

• New: Updated LibLog provider to support structured logging with NLog 4.5. Reduced memory allocations for log4net-provider
• New: Made several methods in AggregateRoot<,> virtual to allow easier customization
• Fixed: Added quoting to the SQL query generator for the column names

  -- query before the fix
    UPDATE [ReadModel-TestAttributes]
    SET UpdatedTime = @UpdatedTime
</tr></table> ... (truncated)

Changelog

Sourced from EventFlow.Autofac's changelog.

New in 0.81 (not released yet)

• Breaking: Elasticsearch NEST Nuget Library updated from v6.1.0 to v7.8.2
• Fixed: You can now create Id : Identity<Id>

New in 0.80.4377 (released 2020-10-01)

• Breaking: To support .NET going forward, all EventFlow test have been converted from .NET Framework 4.x to .NET Core 3.1. This however, introduced a set of breaking changes
  • EntityFramework has been updated from 2.2.6 to 3.1.5
  • IHangfireJobRunner.Execute is now IHangfireJobRunner.ExecuteAsync
• Breaking: Merged AggregateReadStoreManager and SingleAggregateReadStoreManager into one class in order to always guarantee in-order event processing
• Breaking: Marked the UseReadStoreFor<,,,> configuration methods as obsolete, in favor of the simpler overloads with less type parameters (as those automatically figure out the AggregateRoot and Id types and configure the more reliable SingleAggregateReadStoreManager implementation)
• Obsolete: The class AsyncHelper and all non-async methods using it have been marked obsolete and will be removed in EventFlow 1.0 (not planned yet). If you rely on these non-async methods, then merely copy-paste the AsyncHelper from the EventFlow code base and continue using it in your transition to async only
• Fixed: An issue where EntityFrameworkEventPersistence could possibly save aggregate events out of order, which would lead to out-of-order application when streaming events ordered by GlobalSequenceNumber
• New: FilesEventPersistence now uses relative paths
• New: A new set of hook-in interfaces are provided from this release, which should make it easier to implement crash resilience (#439) in EventFlow. Please note that this new API is experimentational and subject to change as different strategies are implemented
  • IAggregateStoreResilienceStrategy
  • IDispatchToReadStoresResilienceStrategy
  • IDispatchToSubscriberResilienceStrategy
  • ISagaUpdateResilienceStrategy

New in 0.79.4216 (released 2020-05-13)

• New: Added .NET Core 3.1 target for the EventFlow and EventFlow.EntityFramework packages
• Added quoting to the SQL query generator for the column names

New in 0.78.4205 (released 2020-05-11)

• New: Updated LibLog provider to support structured logging with NLog 4.5. Reduced memory allocations for log4net-provider
• New: Made several methods in AggregateRoot<,> virtual to allow easier customization
• Fixed: Added quoting to the SQL query generator for the column names

  -- query before the fix
</tr></table> ... (truncated)

Commits

• e128096 Make sure to release packages first
• cffc9b4 The release is 0.81
• a53a185 Prepare next v0 release
• 2515610 Add ISagaErrorHandler<TSaga>
• 39ddf67 Merge pull request #817 from ProH4Ck/feature/generic-saga-error-handler
• cd0575b Move SagaErrorHandler<> search to DispatchToSaga
• 331f7bf Test RootResolver fix
• c1a3761 Fix test and factory implementation
• 7d3a8ce WIP: Specific saga error handler
• 02f24ec Corrected release notes
• Additional 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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #92.