search

Stravaig-Projects / Gedcom

MIT License
0 stars 0 forks source link

Bump Paramore.Brighter from 8.1.1399 to 9.1.16 #151

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps Paramore.Brighter from 8.1.1399 to 9.1.16.

Changelog

Sourced from Paramore.Brighter's changelog.

Release Notes

NuGet packages for the last good build on master are available via AppVeyor (see Artifacts) or the nuget feed is https://ci.appveyor.com/nuget/paramore-brighter-m289d49fraww. The simplest way to work with this is to use the Nuget Feed, which is every successful build, So

When we push a collection of functionality it is available via nuget.org and symbol files are published to symbolsource.org

This section lists features in master, available by AppVeyor, but not yet deployed to nuget.org.

Master

Release 9.1.14

  • Fixed missing negation operator when checking for AWS resources

Release 9.1.14

  • Renamed MessageStore to Outbox and CommandStore to Inbox for clarity with well-known pattern names outside this team
    • Impact is wide, namespaces, class names and project names, so this is a BREAKING CHANGE
    • Mostly you can search and replace to fix
  • Added support for a global inbox via a UseInbox configuration parameter to the Command Processor
    • Will insert an Inbox in all pipelines
    • Can be overriden by a NoGlobalInbox attribute for don't add to pipeline, or an alternative UseInbox attribute to vary config
  • The goal here is to be clearer than our own internal names, which don't help folks who were not part of this team
  • The Outbox now fills up if a producer fails to send. You can set an upper limit on your producer, which is the maximum outstanding messages that you want in the Outbox before we throw an exception. This is not the same as Outbox size limits or sweeper, which is seperate and mainly intended if you don't want the Outbox limit to fail-fast on hitting a limit but keep accumulating results
  • Added caching of attributes on target handlers in the pipeline build step
    • This means we don't do reflection every time we build the pipeline for a request
    • We do still always call the handler factory to instantiate as we don't own handler lifetime, implementer does
    • We added a method to clear the pipeline cache, particularly for testing where you want to test configuration scenarios
  • Added ability to persist RabbitMQ messages
  • Added subscription to blocked/unblocked RMQ channel events. A warning log is created when a channel becomes blocked and an info log is generated when the channel becomes unblocked.
  • Improved the Kafka Client. It now uses the publisher/creator model to ensure that a message is in Brighter format i.e. headers as well as body; updated configuration values; generally improved reliability. This is a breaking change with previous versions of the Kafka client.
  • The class BrighterMessaging now only has a default constructor and now has setters on properties. Use the initializer syntax instead - new BrighterMessage{} to avoid having redundant constructor arguments.
  • Changes to how we configure transports - renaming classes and extending their functionality
    • Connection is renamed to Subscription
    • Added a matching Publication for producers
    • Base class includes the attributes that Brighter Core (Brighter & ServiceActivator) need
    • Derived classes contain transport specific details
    • On SQSConnection, renamed VisibilityTimeout to LockTimeout to more generically describe its purpose seperated from GatewayConfiguration, that now has a marker interface, used to connect to the Gateway and not about how we publish or subscribe
    • We now have the option to declare infastructure separately and Validate or Assume it exists, still have an option to Create which is the default
    • We think it will be most useful for environments like AWS where there is a price to checking (HTTP call, and often looping through results)
    • Added support for a range of parameters that we did not have before such as dead letter queues, security etc via these platform specific configuration files
  • Provided a short form of the BrighterMessaging constructor, that queries object provided for async versions of interfaces
  • Changed IsAsync to RunAsync on a Subscription for clarity
  • Supports an async pipeline: callbacks should happen on the same thread as the handler (and the pump), avoiding thread pool threads
  • Fixed issue in SQlite with SQL to mark a message as dispatched
Commits


Dependabot compatibility score

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[bot] commented 2 years ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.