Bump rails_event_store from 2.18.0 to 2.19.2

[dependabot]

Bumps rails_event_store from 2.18.0 to 2.19.2.

Release notes

Sourced from rails_event_store's releases.

v2.19.2

RubyEventStore

• Add: RubyEventStore::Deprecations — centralized warn-once deprecation warnings
  • use Deprecations.suppress(key) to silence known deprecations in tests
• Change: all runtime deprecation warnings now fire at most once per process
• Fix: transitive deprecation warning for rails_event_store_active_record rename no longer fires spuriously

RailsEventStore

• no changes

RubyEventStore::ActiveRecord

• no changes

AggregateRoot

• no changes

RubyEventStore::RSpec

• no changes

RubyEventStore::Browser

• no changes

v2.19.1

RubyEventStore

• no changes

RailsEventStore

• no changes

RubyEventStore::ActiveRecord

• Fix: migration_for_valid_at_index generator now uses algorithm: :concurrently and disable_ddl_transaction! to prevent table lock on PostgreSQL when running the migration on large event_store_events tables

AggregateRoot

• no changes

RubyEventStore::RSpec

• no changes

... (truncated)

Changelog

Sourced from rails_event_store's changelog.

Releasing RailsEventStore

Maintainer's guide for releasing RailsEventStore and related gems. Hopefully you'll know the drill after reading this.

Versioning policy

We're following Semantic Versioning. We're making our best to describe and communicate breaking changes if such happen.

All gems developed as RailsEventStore distribution will be released with the same version number, even if changes affected only a subset of gems. This is close to the versioning policy of Rails. We do this for convenience not only of maintainers but also to help triaging issues related to particular version.

Contributed gems in contrib/ are not released in RailsEventStore distribution and have a different release cycle.

Communicating changes

All changes across RailsEventStore versions should be documented on changelog. For this purpose, since v0.15.0, we use releases page. Some gems keep individual changelogs prior to the great monorepo merge — they're not updated anymore.

Changes are easier to scan, when they're described with following types:

• Add: for new features
• Change: for changes in existing functionality
• Deprecate: for soon-to-be removed features
• Remove: for now removed features
• Fix: for any bug fixes
• Security: in case of vulnerabilities

Use them following to the full description of introduced change.

When describing changes, list all gems involved gems in the release. Explicitly mention no changes if there were none:

• no changes

When in doubt, check this example

Release steps

1. Draft a new release if that hasn't happened already but don't publish it yet. Leave Tag version field empty by now.
2. Make sure all changes are listed on releases page for undrafted release. When in doubt, use compare view since last release to HEAD of master branch (you may need to modify URL for correct versions to compare).
3. Bump the version number for all gems and dependencies via make set-version RES_VERSION=version_number_here.
4. Hit make release from top-level of repository. This will:

• check of any uncommitted changes

• run unit tests for all involved gems

• tag last commit with version number, ending with a push to to the remote

• build all gem packages

• push built gem packages to RubyGems

  You'll need to have dev_arkency RubyGems API key to complete this step.

5. Go back to releases, link to appropriate git tag in Tag version field. Set title corresponding to version number and publish this release entry.

... (truncated)

Commits

• 67be4ea Version v2.19.2
• f83cf35 Remove redundant table qualifiers in read_from_global_stream select (no JOIN,...
• 2a40b35 Kill alive mutations in Sequel EventRepository: remove dead code, add select(...
• edb72c8 Kill alive mutation in AsyncHandler.prepended by asserting module chain isola...
• 76507ba Format, because of my OCD
• 2777d03 Migrate runtime deprecation warns to Deprecations.warn for warn-once semantics
• b8e04d9 Use Set for O(1) lookups and surface unregistered key errors in Deprecations
• 1c567ca Extract deprecations to AOP-style wrappers in centralized deprecated.rb files
• ebed858 Update APP_TEMPLATE to use AggregateRoot::Repository with explicit injection
• f8e252d Introduce RubyEventStore::Deprecations with warn-once semantics
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)