Update rspec: 3.9.0 → 3.11.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ rspec (3.9.0 → 3.11.0) · Repo

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ rspec-core (indirect, 3.9.2 → 3.11.0) · Repo · Changelog

Release Notes

3.11.0 (from changelog)

Full Changelog

Enhancements:

• Improve pluralisation of words ending with s (like process). (Joshua Pinter, #2779)
• Add ordering by file modification time (most recent first). (Matheus Richard, #2778)
• Add to_s to reserved names for #let and #subject. (Nick Flückiger, #2886)
• Introduce RSpec.current_scope to expose the current scope in which RSpec is executing. e.g. :before_example_hook, :example etc. (@odinhb, #2895)
• Add named bold colours as options for custom colours. (#2913, #2914)
• Warn when (but not prevent) a SystemExit occurs. (Jared Beck, #2926)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ rspec-expectations (indirect, 3.9.2 → 3.11.0) · Repo · Changelog

Release Notes

3.11.0 (from changelog)

Full Changelog

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)

3.10.2 (from changelog)

Full Changelog

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)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ rspec-mocks (indirect, 3.9.1 → 3.11.0) · Repo · Changelog

Release Notes

3.11.0 (from changelog)

Full Changelog

Enhancements:

• Add and_invoke implementation for configuring responses to receive (and receive_messages) with multiple callable objects. (Kyle Smith, #1411)

3.10.3 (from changelog)

Full Changelog

Bug Fixes:

• Suppress warning by setting $VERBOSE to nil. (Nobuyoshi Nakada, #1414)
• Support keyword argument semantics when constraining argument expectations using with on Ruby 3.0+ (Yusuke Endoh, #1394)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ rspec-support (indirect, 3.9.3 → 3.11.0) · Repo · Changelog

Release Notes

3.11.0 (from changelog)

Full Changelog

No changes. Released to support other RSpec releases.

3.10.3 (from changelog)

Full Changelog

Bug Fixes:

• Use Mutex#owned? to allow RSpec::Support::ReentrantMutex to work in nested Fibers on Ruby 3.0 and later. (Benoit Daloze, #503, #504)
• Support end-less methods in RSpec::Support::Source::Token so that RSpec won't hang when an end-less method raises an error. (Yuji Nakayama, #505)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #102.