[src/api] Update clockwork 4.0.0 → 4.0.1 (patch)

[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?

✳️ clockwork (4.0.0 → 4.0.1) · Repo · Changelog

Release Notes

4.0.1

• Update ACTIVE_SUPPORT_VERSION default to 8.1 (81b6cd2)
• Drop test-unit dependency with migrated test (eac1064)
• Remove unused base64, bigdecimal and ostruct dependencies (f171d8f)

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

Commits

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

• Bump version to 4.0.1
• Update ACTIVE_SUPPORT_VERSION default to 8.1 (#92)
• Drop test-unit dependency with migrated test (#93)
• Remove unused base64, bigdecimal and ostruct dependencies (#91)

✳️ minitest (5.27.0 → 6.0.2) · Repo · Changelog

Release Notes

6.0.2 (from changelog)

• 7 bug fixes:

  • Added missing drb dependency from minitest-server. (y-yagi)

  • Cleaned up bisect’s sub-commands to load files directly, not ruby+require.

  • Fixed bisect to use same cmd ($0) to run tests as original invocation.

  • load server_plugin if server is loaded. (y-yagi)

  • Manipulate local args instead of ARGV in Sprint.run.

  • Only show –bisect in usage if using minitest.

  • Remove -Itest:lib from bisect’s rb_flags since bin/minitest adds them.

6.0.1 (from changelog)

• 1 minor enhancement:

  • Added new rake task ‘test:fu` to Minitest::TestTask, to only run tests with FU (focused units?) in their name. This should mostly obviate the need for the minitest-focus plugin.

• 5 bug fixes:

  • Fixed –help and –version exiting 1. (grosser)

  • Fixed method signature of Minitest::Benchmark.run. (flavorjones)

  • Flush stdout/stderr before exit./bin/minitest -Ilib ./bug1046.rb:1 < /dev/null (grosser)

  • Improved usage banner output by reordering and reformatting.

  • Normalize paths while processing file.rb:line args.

6.0.0 (from changelog)

This is a major release. Read this.

Please give feedback here: github.com/minitest/minitest/issues/1040

Oh god… here we go… (again)

• 8 deaths in the family(!!):

  • Deleted MiniTest and MiniTest::Unit::TestCase compatibility namespaces.

  • Deleted all use of Marshal for serialization.

  • Deleted maglev? and rubinius? guard methods. LOL.

  • Deleted all minitest/spec expectations from Object. Use _/value/expect.

  • Dropped minitest/mock.rb. This has been extracted to the minitest-mock gem.

  • assert_equal(nil, value) no longer allowed. Use assert_nil to be explicit.

  • Removed assert_send. Use assert_predicate or assert_operator.

  • Removed Minitest::Test#class_name.

• 7 major (oft incompatible) changes:

  • Big: Major refactored MT6’s run path!

    • Minitest.__run -> Minitest.run_all_suites

    • Runnable.run -> Runnable.run_suite & Runnable.filter_runnable_methods

    • Runnable.run_one_method -> Runnable.run

    • Removed Minitest.run_one_method (might bring it back to raise?)

  • Removed deprecated ENV["N"] to specify number of parallel tests. Use MT_CPU.

  • Renamed options[:filter] to options[:include], added --include cmdline option.

    • --name is still handled, but that will be removed in the future.

  • Renamed Minitest::Runnable#test_order to #run_order.

  • If #message is passed a proc then that proc overrides all other output.

    • They are no longer chained!

    • And it does less for formatting of your output.

  • Removed reporter arg from with_info_handler as it has never(?) been used. (HACK?)

  • Plugin loading is now opt-in!

    • Require the plugin in your test_helper.

    • Or use Minitest.load :x

    • Or call Minitest.load_plugins for the old autoloading behavior.

• 5 additions:

  • Added minitest-sprint’s minitest cmdline, now with line support!

  • Added minitest-bisect. Run with minitest –bisect or -b.

  • Added minitest-server.

  • Added minitest/complete to help with shell’s tab-completion of tests.

  • Vendored latest version of path_expander.

• 5 other:

  • Bumped to ruby 3.2+.

  • Removed obsolete conditional for CompositeReporter#prerecord.

  • Removed obsolete version guards around Minitest::Result in reporters.

  • assert_operator and assert_predicate both call assert_respond_to first.

  • Assertions reuse themselves a lot more. Bumps assertion count in some places.

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

Commits

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

• prepped for release
• Fixed some doco coverage... still running into tons of pain with rdoc.
• - Fixed bisect to use same cmd ($0) to run tests as original invocation.
• y-yagi is smart and I am dum
• - Only show --bisect in usage if using minitest.
• Push up server_plugin fix to minitest.rb guarded by env.
• Fixed up tests to be line independent.
• - MT6: load server_plugin if server is loaded. (y-yagi)
• - Manipulate local args instead of ARGV in Sprint.run.
• Added new rdoc rsync location.
• - Added missing drb dependency from minitest-server. (y-yagi)
• Normalize CI workflow so I can use the same file across a number of projects.
• sort manifest. oops
• remove rematch and add minitest-holdify to plugin list
• prepped for release
• - Fixed method signature of Minitest::Benchmark.run. (flavorjones)
• - Flush stdout/stderr before exit./bin/minitest -Ilib ./bug1046.rb:1 < /dev/null (grosser)
• - Normalize paths while processing file.rb:line args.
• - Fixed --help and --version exiting 1. (grosser)
• - Improved usage banner output by reordering and reformatting.
• + Added new rake task `test:fu` to Minitest::TestTask, to only run tests with FU in name.
• Fix format of History.rdoc. (y-yagi)
• prepped for release
• Add Hoe's :cov plugin and start to look at gaps
• - Removed MT5's post_install_message.
• - Bumped to ruby 3.2+
• - Removed obsolete version guards around Minitest::Result in reporters.
• - Removed obsolete conditional for CompositeReporter#prerecord.
• + Added minitest/complete to help with shell's tab-completion of tests.
• + Renamed options[:filter] to options[:include], added --include cmdline option.
• + If message is passed a proc then that proc overrides all other output.
• + Assertions reuse themselves a lot more. Bumps assertion count in some places.
• + assert_operator and assert_predicate both call assert_respond_to first.
• + Vendored latest version of path_expander.
• ! Added minitest-bisect. Run with minitest --bisect or -b.
• ! Added minitest-server.
• ! Added minitest-sprint's minitest cmdline.
• ! Removed reporter arg from with_info_handler as it has never(?) been used. (HACK?)
• ! Dropped minitest/mock.rb. This will be extracted to its own gem.
• ! Renamed Minitest::Runnable#test_order to run_order.
• ! Removed deprecated ENV["N"] to specify number of parallel tests. Use MT_CPU.
• ! Big: Refactored MT6's run path!
• ! Plugin loading is now opt-in!
• ! Deleted all minitest/spec expectations from Object. Use _/value/expect.
• ! Removed Minitest::Test#class_name.
• ! Removed assert_send.
• ! assert_equal(nil, value) no longer allowed. Use assert_nil to be explicit.
• ! Deleted maglev? and rubinius? guard methods.
• ! Deleted all use of Marshal for serialization.
• ! Deleted MiniTest and MiniTest::Unit::TestCase compatibility namespaces.

↗️ connection_pool (indirect, 2.5.5 → 3.0.2) · Repo · Changelog

Release Notes

3.0.2 (from changelog)

• Support :name keyword for backwards compatibility [#210]

3.0.1 (from changelog)

• Add missing fork.rb to gemspec.

3.0.0 (from changelog)

• BREAKING CHANGES ConnectionPool and ConnectionPool::TimedStack now use keyword arguments rather than positional arguments everywhere. Expected impact is minimal as most people use the with API, which is unchanged.

pool = ConnectionPool.new(size: 5, timeout: 5)
pool.checkout(1) # 2.x
pool.reap(30)    # 2.x
pool.checkout(timeout: 1) # 3.x
pool.reap(idle_seconds: 30) # 3.x

• Dropped support for Ruby <3.2.0

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

Commits

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

• bump, changes
• Support :name keyword arg for backwards compat, #210
• Fix missing fork.rb
• docs
• refactor idle reaping for readability
• fix CI warning
• fork refactoring
• ci tuning
• Connection Pool 3.0 (#209)
• Add benchmark to validate fast path performance

---

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)

[github-actions]

Please see the links listed bellow to review the changes applied to the gems:

• clockwork 4.0.0 -> 4.0.1
• connection_pool 2.5.5 -> 3.0.2
• minitest 5.27.0 -> 6.0.2

[eduardoj]

@depfu rebase

[saraycp]

I wonder if forcing activesupport to version 8.1 would be a problem for our project which still uses activesupport 7.2.3.

Rykian/clockwork@81b6cd2#diff-d09ea66f8227784ff4393d88a19836f321c915ae10031d16c93d67e6283ab55fR7

[eduardoj]

I wonder if forcing activesupport to version 8.1 would be a problem for our project which still uses activesupport 7.2.3.

If I'm not mistaken, that change only updated the default version used to run the gem's internal tests to 8.1 in their own development environment.

If we want to be strictly conservative, we could hold the upgrade. The rubygem is currently not tested with Rails 7.2.

However, looking at the recent commits, there are no structural changes that suggest compatibility issues with Rails 7.2. A quick check on our development environment or in our staging machine should be enough to confirm we can upgrade safely without any dependency conflicts.