search

sanger / unified_warehouse

MIT License
2 stars 8 forks source link

Update rspec-rails 6.1.4 → 6.1.5 (patch) #669

Closed depfu[bot] closed 2 months ago

depfu[bot] commented 2 months 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 (6.1.4 → 6.1.5) · Repo · Changelog

Release Notes

6.1.5 (from changelog)

Full Changelog

Bug Fixes:

  • Restore old order of requiring support files. (Franz Liedke, #2785)
  • Prevent running rake spec:statsetup on Rails main / 8.0.0. (Petrik de Heus, #2781)

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

Commits

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

↗️ rspec-core (indirect, 3.13.0 → 3.13.1) · Repo · Changelog

Commits

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

↗️ rspec-expectations (indirect, 3.13.1 → 3.13.2) · Repo · Changelog

Release Notes

3.13.2 (from changelog)

Bug Fixes:

  • When using null object doubles, prevent typos triggering dynamic matchers. (Eric Mueller, #1455)
  • Use RSpec.warning for an expectation warning rather than Kernel.warn. (Jon Rowe, #1472)
  • Prevent mismatched use of block and value matchers in compound expectations. (Phil Pirozhkov, #1476)
  • Raise an error when passing no arguments to the include matcher. (Eric Mueller, #1479)

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

Commits

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

↗️ thor (indirect, 1.3.1 → 1.3.2) · Repo · Changelog

Release Notes

1.3.2

What's Changed

New Contributors

Full Changelog: v1.3.1...v1.3.2

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

Commits

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

↗️ zeitwerk (indirect, 2.6.17 → 2.6.18) · Repo · Changelog

Release Notes

2.6.18 (from changelog)

  • Fixes a bug in which projects reopening the main namespace of a gem dependency managed by its own Zeitwerk loader could not reload the constants they added to that external namespace.

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

Commits

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

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)