Update rspec-rails 6.1.3 → 6.1.4 (patch)

[depfu[bot]]

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.3 → 6.1.4) · Repo · Changelog

Release Notes

6.1.4 (from changelog)

Full Changelog

Bug Fixes:

• Prevent have_http_status matcher raising an error when encountering a raw Rack::MockResponse. (Christophe Bliard, #2771)
• Move Rails version conditional from index scaffold generated file to template. (Matt Jankowski, #2777)

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

Commits

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

• 6.1.4
• Extract `cell_selector` method in scaffold index view spec generator (#2777)
• Changelog for #2771
• Merge pull request #2771 from cbliard/support-rack-mock-response-with-have-http-status
• Create SECURITY.md
• Merge pull request #2770 from toshimaru/use-perform_enqueued_jobs

↗️ concurrent-ruby (indirect, 1.3.3 → 1.3.4) · Repo · Changelog

Release Notes

1.3.4

What's Changed

• Update comment for JRuby variant of processor_count to reality by @meineerde in #1054
• Add Concurrent.cpu_requests that is cgroups aware. by @heka1024 in #1058
• Fix the doc of Concurrent.available_processor_count by @y-yagi in #1059
• Fix the return value of Concurrent.available_processor_count when cpu.cfs_quota_us is -1 by @y-yagi in #1060

New Contributors

• @heka1024 made their first contribution in #1058
• @y-yagi made their first contribution in #1059

Full Changelog: v1.3.3...v1.3.4

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

Commits

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

• Avoid requiring files of the gem in Rakefile to avoid redefined method warnings
• Avoid require in Gemfile & Rakefile to avoid redefined constant warnings
• Avoid require in *.gemspec files to avoid redefined constant warnings
• Update docs-source/signpost.md
• 1.3.4
• Check early that $CONCURRENT_JRUBY_HOME is set
• Fix the return value of `Concurrent.available_processor_count` when `cpu.cfs_quota_us` is -1
• Fix the doc of `Concurrent.available_processor_count`
• Add `Concurrent.cpu_shares` that is cgroups aware.
• Update comment for JRuby variant of processor_count to reality

↗️ minitest (indirect, 5.24.1 → 5.25.1) · Repo · Changelog

Release Notes

5.25.0 (from changelog)

• 2 minor enhancements:

  • Fixed some inefficiencies filtering and matching (mostly backtraces).

  • Refactored siginfo handler to reduce runtime costs. Saved ~30%!

• 5 bug fixes:

  • Added missing rdoc to get back to 100% coverage.

  • Cleaning up ancient code checking for defined?(Encoding) and the like.

  • Disambiguated some shadowed variables in minitest/compress.

  • Fixed an ironic bug if using string-literals AND Werror.

  • Improve description of test:slow task. (stomar)

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

Commits

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

• prepped for release
• - Fix incompatibility caused by minitest-hooks & rails invading minitest internals.
• - Revert change from =~ to match? to allow for nil if $TERM undefined.
• prepped for release
• + Refactored siginfo handler to reduce runtime costs. Saved ~30%!
• normalized all actual/expected var names for assert_equal tests
• Accept colon style Hash#inspect in test. (tompng)
• - Improve description of test:slow task. (stomar)
• - Cleaning up ancient code checking for defined?(Encoding) and the like.
• Minor fix to make deprecation tests pass when using rake testW0
• oops
• + Fixed some inefficiencies filtering and matching (mostly backtraces).
• More foolish consistency...
• More foolish consistency... "So many parens!" edition
• More foolish consistency...
• "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers and divines"—Emerson
• - Disambiguated some shadowed variables in minitest/compress.
• Got rid of ANCIENT pre-Integer-merge tests
• Got rid of ANCIENT RUBY18 conditioned tests
• - Fixed an ironic bug if using string-literals AND Werror.
• Finally removed all clean + heredoc for squiggly heredocs in test.
• - Added missing rdoc to get back to 100% coverage.
• Double quoted some (ancient) string literals.
• Fixed 3 tests when using minitest-gcstats.

↗️ nokogiri (indirect, 1.16.6 → 1.16.7) · Repo · Changelog

Release Notes

1.16.7

v1.16.7 / 2024-07-27

Dependencies

• [CRuby] Vendored libxml2 is updated to v2.12.9, which the upstream release notes state is a security release to address CVE-2024-40896. Nokogiri's maintainers believe this vulnerability does not affect users of Nokogiri, but we advise upgrading at your earliest convenience anyway.

---

sha256 checksums:

78778d35f165b59513be31c0fe232c63a82cf97626ffba695b5f822e5da1d74b  nokogiri-1.16.7-aarch64-linux.gem
c84cdb9e3aa44c35bbb981b20175838c4b2066c26c5cb118f31f177168a42fc3  nokogiri-1.16.7-arm-linux.gem
276dcea1b988a5b22b5acc1ba901d24b8e908c40b71dccd5d54a2ae279480dad  nokogiri-1.16.7-arm64-darwin.gem
044c45ca46abc2b6135a85ab39a546ff2f0434d43142bc59b83e5b1068876a42  nokogiri-1.16.7-java.gem
01ed785392f9cbdfd45e0e5ef6ad6d2c80a6128672589448f18952168bd68e56  nokogiri-1.16.7-x64-mingw-ucrt.gem
d8fd5c675743b85354c9098117bfa9e703c7cacab8c33e5190104ea8218ad1ec  nokogiri-1.16.7-x64-mingw32.gem
dddbf1c1ef99ce9fab98302b14f8bacb703e6f16e89b99f05ecee8a1fca23664  nokogiri-1.16.7-x86-linux.gem
b6517d995b024739cbb81251a26866d40e1ccb151936b5bb0977e7487f4e617c  nokogiri-1.16.7-x86-mingw32.gem
630732b80fc572690eab50c73a1f18988f3ac401ed0b67ca9956ba2b1e2c3faa  nokogiri-1.16.7-x86_64-darwin.gem
9e1e428641d5942af877c60b418c71163560e9feb4a5c4015f3230a8b86a40f6  nokogiri-1.16.7-x86_64-linux.gem
f819cbfdfb0a7b19c9c52c6f2ca63df0e58a6125f4f139707b586b9511d7fe95  nokogiri-1.16.7.gem

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

Commits

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

• version bump to v1.16.7
• dep: update libxml2 to v2.12.9 (branch v1.16.x) (#3297)
• dep: update packaged libxml2 to v2.12.9

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

Release Notes

2.6.17 (from changelog)

• Fix log message when eager loading a directory ends.

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

Commits

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

• Ready for 2.6.17
• Fix log message when eager loading a directory ends

---

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)