search

isleofruby / isleofruby-activities

organise activities around your conference
Other
1 stars 1 forks source link

Update rspec-rails 3.7.2 → 3.9.1 (minor) #302

Closed depfu[bot] closed 1 year ago

depfu[bot] commented 1 year ago

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-rails (3.7.2 → 3.9.1) · Repo · Changelog

Release Notes

3.9.0 (from changelog)

Full Changelog

Enhancements

  • Use __dir__ instead of __FILE__ in generated rails_helper.rb where supported. (OKURA Masafumi, #2048)
  • Add have_enqueued matcher as a "super" matcher to the ActiveJob matchers making it easier to match on ActiveJob delivered emails. (Joel Lubrano, #2047)
  • Add generator for system specs on Rails 5.1 and above. (Andrzej Sliwa, #1933)
  • Add generator for generator specs. (@ConSou, #2085)
  • Add option to generate routes when generating controller specs. (David Revelo, #2134)

Bug Fixes:

  • Make the ActiveJob matchers fail when multiple jobs are queued for negated matches. e.g. `expect { job; job; }.to_not have_enqueued_job. (Emric Istanful, #2069)

3.8.3 (from changelog)

Full Changelog

Bug Fixes:

  • Namespaced fixtures now generate a / seperated path rather than an _. (@nxlith, #2077)
  • Check the arity of errors before attempting to use it to generate the be_valid error message. (Kevin Kuchta, #2096)

3.8.2 (from changelog)

Full Changelog

Bug Fixes:

  • Fix issue with generator for preview specs where Mailer would be duplicated in the name. (Kohei Sugi, #2037)
  • Fix the request spec generator to handle namespaced files. (Kohei Sugi, #2057)
  • Further truncate system test filenames to handle cases when extra words are prepended. (Takumi Kaji, #2058)
  • Backport: Make the ActiveJob matchers fail when multiple jobs are queued for negated matches. e.g. `expect { job; job; }.to_not have_enqueued_job (Emric Istanful, #2069)

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 (indirect, 3.7.0 → 3.9.0) · Repo

Commits

See the full diff on Github. The new version differs by 8 commits:

↗️ rspec-core (indirect, 3.7.1 → 3.9.3) · Repo · Changelog

Release Notes

3.9.1 (from changelog)

Full Changelog

Bug Fixes:

  • Prevent bisect command from blocking when number of specs exceeds file descriptor limit on OSX or Linux. (Benoit Tigeot, #2669)
  • Prevent warnings being issued on Ruby 2.7.0. (Jon Rowe, #2680)

3.9.0 (from changelog)

Full Changelog

Enhancements:

  • Improve the handling of errors during loading support files, if a file errors before loading specs, RSpec will now skip loading the specs. (David Rodríguez, #2568)
  • Add support for --example-matches to run examples by regular expression. (Sam Joseph, Matt Rider, @okothkongo1, #2586)
  • Add did_you_mean suggestions for file names encountering a LoadError outside of examples. (@obromios, #2601)
  • Add a minimalist quick fix style formatter, only outputs failures as file:line:message. (Romain Tartière, #2614)
  • Convert string number values to integer when used for RSpec::Configuration#fail_fast (Viktor Fonic, #2634)
  • Issue warning when invalid values are used for RSpec::Configuration#fail_fast (Viktor Fonic, #2634)
  • Add support for running the Rake task in a clean environment. (Jon Rowe, #2632)
  • Indent messages by there example group / example in the documentation formatter. (Samuel Williams, #2649)

3.8.2 (from changelog)

Full Changelog

Bug Fixes:

  • Fix config.define_derived_metadata so that cascades are not triggered until metadata has been assigned to the example or example group (Myron Marston, #2635).

3.8.1 (from changelog)

Full Changelog

Bug Fixes:

  • Handle RSpec description(s) with japanese chars in CP932 encoded files. (Benoit Tigeot, #2575)
  • When defining let methods that overwrite an existing method, prevent a warning being issued by removing the old definition. (Jon Rowe, #2593)
  • Prevent warning on Ruby 2.6.0-rc1 (Keiji Yoshimi, #2582)
  • Fix config.define_derived_metadata so that it supports cascades. (Myron Marston, #2630).

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.7.0 → 3.9.4) · Repo · Changelog

Release Notes

3.9.2 (from changelog)

Full Changelog

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)

3.9.0 (from changelog)

Full Changelog

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)

3.8.6 (from changelog)

Bug Fixes:

  • Revert #1125 due to the change being incompatible with our semantic versioning policy.

3.8.5 (from changelog)

Full Changelog

Bug Fixes:

  • Prevent unsupported implicit block expectation syntax from being used. (Phil Pirozhkov, #1125)

3.8.4 (from changelog)

Full Changelog

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)

3.8.3 (from changelog)

Full Changelog

Bug Fixes:

  • Prevent composed all matchers from leaking into their siblings leading to duplicate failures. (Jamie English, #1086)
  • Prevent objects which change their hash on comparison from failing change checks. (Phil Pirozhkov, #1110)
  • Issue an ArgumentError rather than a NoMethodError when be_an_instance_of and be_kind_of matchers encounter objects not supporting those methods. (Taichi Ishitani, #1107)

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.7.0 → 3.9.1) · Repo · Changelog

Release Notes

3.9.1 (from changelog)

Full Changelog

Bug Fixes:

  • Trigger RSpec::Mocks.configuration.verifying_double_callbacks when using allow_any_instance_of or expect_any_instance_of (Daniel Orner, #1309)

3.9.0 (from changelog)

Full Changelog

Enhancements:

  • Improve thread safety of message expectations by using Mutex to prevent deadlocking errors. (Ry Biesemeyer, #1236)
  • Add the ability to use time as an alias for times. For example: expect(Class).to receive(:method).exactly(1).time. (Pistos, Benoit Tigeot, #1271)

3.8.2 (from changelog)

Full Changelog

  • Allow array_including argument matchers to be nested. (Emmanuel Delmas, #1291)

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.7.1 → 3.9.4) · Repo · Changelog

Release Notes

3.9.2 (from changelog)

Full Changelog

Bug Fixes:

  • Remove unneeded eval. (Matijs van Zuijlen, #394)

3.9.1 (from changelog)

Full Changelog

Bug Fixes:

  • Remove warning caused by keyword arguments on Ruby 2.7.0. (Jon Rowe, #392)

3.9.0 (from changelog)

Full Changelog

NO CHANGES

Version 3.9.0 was released to allow other RSpec gems to release 3.9.0.

3.8.3 (from changelog)

Bug Fixes:

  • Escape \r when outputting strings inside arrays. (Tomita Masahiro, Jon Rowe, #378)
  • Ensure that optional hash arguments are recognised correctly vs keyword arguments. (Evgeni Dzhelyov, #366)

3.8.2 (from changelog)

Full Changelog

Bug Fixes:

  • Ensure that optional hash arguments are recognised correctly vs keyword arguments. (Evgeni Dzhelyov, #366)
  • Ensure that an empty hash is recognised as empty keyword arguments when applicable. (Thomas Walpole, #375)
  • Ensure that diffing truthy values produce diffs consistently. (Lucas Nestor, #377)

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.

Depfu Status

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 cancel merge
Cancels automatic merging of this PR
@​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)