rubygem-rspec-expectations-3.12.0-160000.2.2

updated to version 3.12.0
  see installed Changelog.md

updated to version 3.11.1
  see installed Changelog.md

updated to version 3.11.0
  see installed Changelog.md
  Enhancements:
  * Return `true` from `aggregate_failures` when no exception occurs. (Jon Rowe, #1225)
  Deprecations:
  * Print a deprecation message when using the implicit block expectation syntax.
    (Phil Pirozhkov, #1139)

updated to version 3.10.2
  see installed Changelog.md
  [#]## Development
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.10.2...3-10-maintenance)
  [#]## 3.10.2 / 2022-01-14
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.10.1...v3.10.2)
  Bug Fixes:
  * Fix support for dynamic matchers for expectation target checks (Phil Pirozhkov, #1294)
  * Fix `expect(array).to include(hash).times`, previously this would fail due to
    matching the entire array as a single hash, rather than a member of the hash.
    (Slava Kardakov, #1322)
  * Ensure `raise_error` matches works with the `error_highlight` option from Ruby 3.1.
    (Peter Goldstein, #1339)

- updated to version 3.10.1
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.10.0...v3.10.1)
  Bug Fixes:
  * Allow JRuby 9.2.x.x to generate backtraces normally rather than via our
    backfill workaround. (#1230, Jon Rowe)

- updated to version 3.10.0
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.9.3...v3.10.0)
  Enhancements:
  * Allow `include` matcher to be chained with `once`, `at_least`, etc. for simple cases.
    (Marc-André Lafortune, #1168)
  * Add an explicit warning when `nil` is passed to `raise_error`. (Phil Pirozhkov, #1143)
  * Improve `include` matcher's composability. (Phil Pirozhkov, #1155)
  * Mocks expectations can now set a custom failure message.
    (Benoit Tigeot and Nicolas Zermati, #1156)
  * `aggregate_failures` now shows the backtrace line for each failure. (Fabricio Bedin, #1163)
  * Support multiple combinations of `yield_control` modifiers like `at_least`, `at_most`.
    (Jon Rowe, #1169)
  * Dynamic `have_<n>` matchers now have output consistent with other dynamic matchers.
    (Marc-André Lafortune, #1195)
  * New config option `strict_predicate_matchers` allows predicate matcher to be strict
    (i.e. match for `true` or `false`) instead of the default (match truthy vs `false` or `nil`).
    (Marc-André Lafortune, #1196)

- updated to version 3.9.2
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.9.1...v3.9.2)
  Bug Fixes:
  * Issue a proper `ArgumentError` when invalid arguments are given to `yield_control`
    modifiers such as `at_least` et al. (Marc-André Lafortune, #1167)
  * Prevent Ruby 2.7 keyword arguments warning from being issued by custom
    matcher definitions. (Jon Rowe, #1176)

- updated to version 3.9.1
  * no changelog for version 3.9.1 found

- updated to version 3.9.0
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.6...v3.9.0)
  Enhancements:
  * The `respond_to` matcher now uses the signature from `initialize` to validate checks
    for `new` (unless `new` is non standard). (Jon Rowe, #1072)
  * Generated descriptions for matchers now use `is expected to` rather than `should` in
    line with our preferred DSL. (Pete Johns, #1080, rspec/rspec-core#2572)
  * Add the ability to re-raise expectation errors when matching
    with `match_when_negated` blocks. (Jon Rowe, #1130)
  * Add a warning when an empty diff is produce due to identical inspect output.
    (Benoit Tigeot, #1126)

- updated to version 3.8.4
  [Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.3...v3.8.4)
  Bug Fixes:
  * Prevent false negatives when checking objects for the methods required to run the
    the `be_an_instance_of` and `be_kind_of` matchers. (Nazar Matus, #1112)