December 2025 - ruby-talk - ml.ruby-lang.org

[ruby-talk:444733] [ANN] flog 4.9.1 Released
by Ryan Davis 20 Dec '25

20 Dec '25

flog version 4.9.1 has been released! * home: <http://ruby.sadi.st/> * code: <https://github.com/seattlerb/flog> * rdoc: <http://docs.seattlerb.org/flog> * vim: <http://github.com/sentientmonkey/vim-flog> Flog reports the most tortured code in an easy to read pain report. The higher the score, the more pain the code is in. Changes: ### 4.9.1 / 2025-12-20 * 4 bug fixes: * Bumped dependency to prism to get some upstreamed fixes. * Dropped ruby_parser dependency (now considered soft dep for --legacy flag). * Minor cleanup of some of the upstreamed fixes. * Re-add ruby_parser dependency until I can get a patch into prism to loosen it up.

1 0

[ruby-talk:444732] [ANN] flay 2.14.1 Released
by Ryan Davis 20 Dec '25

20 Dec '25

flay version 2.14.1 has been released! * home: <http://ruby.sadi.st/> * code: <https://github.com/seattlerb/flay> * rdoc: <http://docs.seattlerb.org/flay/> Flay analyzes code for structural similarities. Differences in literal values, variable, class, method names, whitespace, programming style, braces vs do/end, etc are all ignored. Making this totally rad. Changes: ### 2.14.1 / 2025-12-20 * 3 bug fixes: * Bumped dependency to prism to get some upstreamed fixes. * Loosened the minitest dependency to include MT6. * Removed local copy of the upstreamed fixes.

1 0

[ruby-talk:444731] [ANN] ruby_parser 3.22.0 Released
by Ryan Davis 20 Dec '25

20 Dec '25

ruby_parser version 3.22.0 has been released! * home: <https://github.com/seattlerb/ruby_parser> * bugs: <https://github.com/seattlerb/ruby_parser/issues> * rdoc: <http://docs.seattlerb.org/ruby_parser> ruby_parser (RP) is a ruby parser written in pure ruby (utilizing racc--which does by default use a C extension). It outputs s-expressions which can be manipulated and converted back to ruby via the ruby2ruby gem. As an example: def conditional1 arg1 return 1 if arg1 == 0 return 0 end becomes: s(:defn, :conditional1, s(:args, :arg1), s(:if, s(:call, s(:lvar, :arg1), :==, s(:lit, 0)), s(:return, s(:lit, 1)), nil), s(:return, s(:lit, 0))) Tested against 801,039 files from the latest of all rubygems (as of 2013-05): * 1.8 parser is at 99.9739% accuracy, 3.651 sigma * 1.9 parser is at 99.9940% accuracy, 4.013 sigma * 2.0 parser is at 99.9939% accuracy, 4.008 sigma * 2.6 parser is at 99.9972% accuracy, 4.191 sigma * 3.0 parser has a 100% parse rate. * Tested against 2,672,412 unique ruby files across 167k gems. * As do all the others now, basically. Changes: ### 3.22.0 / 2025-12-20 * 1 major enhancement: * Announced the EOL of ruby_parser! YAY! * 6 minor enhancements: * 3.3: working down the grammar structural differences. * Added tentative 3.4 support. * Renamed assignable to old_assignable and added newer cleaner assignable * Restructured comparison rake tasks and normalization to deal with lrama changes. * Updated compare versions and added 3.4. * Updated grammars to fit most closely to ruby 3.2. Working it down the line. * 11 bug fixes: * Always raise RubyParser::SyntaxError (wrap and raise). * Bumped ruby version to 3.2+. * Cleaned up user_variable productions to always return sexps. * Corrections and enhancements for gauntlet.md instructions. * Fixed rake compare's clean subtask to nuke the unpacked ruby dirs entirely. * Fixed superclass of V34. * Fixed up a couple errors created by using STRICT_SEXP=2. 3 will be neigh impossible. * I am nothing if not stubborn: fixed errors caused by STRICT_SEXP=3. * Minor fixes for 3.2+ grammars on "defined?" expressions. * Removed a lot of ancient compatibility checks and patches. (eg encodings) * This in turn cleaned up var_ref and a bunch of other productions.

1 0

[ruby-talk:444730] Recommended Plan for Migrating from React.js To Opal Ruby & Glimmer DSL for Web
by Andy Maleh 19 Dec '25

19 Dec '25

In a recent team retrospective meeting at my job, 5 team devs (all) voted for the future plan item "More use of Opal Ruby & Glimmer DSL for Web in the Rails Web App Frontend". We are following a gradual rollout plan for migrating our React.js Frontend to Opal Ruby & Glimmer DSL for Web inside our Fintech Ruby on Rails web application. Continue reading article: https://andymaleh.blogspot.com/2025/12/recommended-plan-for-migration-from.…

1 0

[ruby-talk:444729] [ANN] minitest-mock 5.27.0 Released
by Ryan Davis 18 Dec '25

18 Dec '25

minitest-mock version 5.27.0 has been released! * home: <https://minite.st/> * code: <https://github.com/minitest/minitest-mock> * bugs: <https://github.com/minitest/minitest-mock/issues> * rdoc: <https://docs.seattlerb.org/minitest-mock> * clog: <https://github.com/minitest/minitest-mock/blob/main/History.rdoc> minitest/mock, by Steven Baker, is a beautifully tiny mock (and stub) object framework. The minitest-mock gem is an extraction of minitest/mock.rb from minitest in order to make it easier to maintain independent of minitest. Changes: ### 5.27.0 / 2025-12-18 * No changes

1 0

[ruby-talk:444727] [ANN] minitest 6.0.0 Released
by Ryan Davis 17 Dec '25

17 Dec '25

minitest version 6.0.0 has been released! * home: <https://minite.st/> * code: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * emacs: <https://github.com/arthurnn/minitest-emacs> * vim: <https://github.com/vim-test/vim-test> minitest provides a complete suite of testing facilities supporting TDD, BDD, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 6.0.0 / 2025-12-17 This is a major release. Read this. Please give feedback here: https://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.

2 1

[ruby-talk:444726] [ANN] minitest 6.0.0.a1 Released
by Ryan Davis 16 Dec '25

16 Dec '25

minitest version 6.0.0.a1 has been released! * home: <https://minite.st/> * code: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * emacs: <https://github.com/arthurnn/minitest-emacs> * vim: <https://github.com/vim-test/vim-test> minitest provides a complete suite of testing facilities supporting TDD, BDD, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 6.0.0.a.1 / 2025-12-15 This is an alpha level release in order to get feedback. I'm pretty settled on integrating minitest-sprint's minitest cmdline but less sold on having bisect+server integrated. Please give me feedback here: https://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. * 1 voodoo: * HACK: does anyone require minitest/test w/o minitest? that's crazy right?

1 0

[ruby-talk:444725] [ANN] minitest-mock 5.27.0.beta.1 Released
by Ryan Davis 11 Dec '25

11 Dec '25

minitest-mock version 5.27.0.beta.1 has been released! minitest/mock, by Steven Baker, is a beautifully tiny mock (and stub) object framework. The minitest-mock gem is an extraction of minitest/mock.rb from minitest in order to make it easier to maintain independent of minitest. Changes: ### 5.27.0.beta.1 / 2025-12-11 * 1 major enhancement: * Extracted from minitest into an independent minitest-mock gem! # Historical Record: The rest of this document is here for historical purposes only. It reflects all of the changes to minitest, not just minitest/mock.rb.

1 0

[ruby-talk:444724] worker_bee 1.0.0 and flay 2.14.0 release emails are missing
by Ryan Davis 11 Dec '25

11 Dec '25

Rate limiting maybe? 🤣 https://www.zenspider.com/releases/2025/12/worker_bee-version-1-0-0-has-bee… https://www.zenspider.com/releases/2025/12/flay-version-2-14-0-has-been-rel…

1 0

[ruby-talk:444723] [ANN] minitest 5.27.0 Released
by Ryan Davis 11 Dec '25

11 Dec '25

minitest version 5.27.0 has been released! * home: <https://minite.st/> * code: <https://github.com/minitest/minitest> * bugs: <https://github.com/minitest/minitest/issues> * rdoc: <https://docs.seattlerb.org/minitest> * clog: <https://github.com/minitest/minitest/blob/master/History.rdoc> * emacs: <https://github.com/arthurnn/minitest-emacs> * vim: <https://github.com/vim-test/vim-test> minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking. "I had a class with Jim Weirich on testing last week and we were allowed to choose our testing frameworks. Kirk Haines and I were paired up and we cracked open the code for a few test frameworks... I MUST say that minitest is *very* readable / understandable compared to the 'other two' options we looked at. Nicely done and thank you for helping us keep our mental sanity." -- Wayne E. Seguin minitest/test is a small and incredibly fast unit testing framework. It provides a rich set of assertions to make your tests clean and readable. minitest/spec is a functionally complete spec engine. It hooks onto minitest/test and seamlessly bridges test assertions over to spec expectations. minitest/benchmark is an awesome way to assert the performance of your algorithms in a repeatable manner. Now you can assert that your newb co-worker doesn't replace your linear algorithm with an exponential one! minitest/mock by Steven Baker, is a beautifully tiny mock (and stub) object framework. minitest/pride shows pride in testing and adds coloring to your test output. I guess it is an example of how to write IO pipes too. :P minitest/test is meant to have a clean implementation for language implementors that need a minimal set of methods to bootstrap a working test suite. For example, there is no magic involved for test-case discovery. "Again, I can't praise enough the idea of a testing/specing framework that I can actually read in full in one sitting!" -- Piotr Szotkowski Comparing to rspec: rspec is a testing DSL. minitest is ruby. -- Adam Hawkins, "Bow Before MiniTest" minitest doesn't reinvent anything that ruby already provides, like: classes, modules, inheritance, methods. This means you only have to learn ruby to use minitest and all of your regular OO practices like extract-method refactorings still apply. Changes: ### 5.27.0 / 2025-12-11 * 1 major enhancement: * Adding post install message announcing the EOL for minitest 5! * 2 minor enhancements: * Removed TestTask::Work#initialize since Queue can now initialize with an Enumerable! AMAZING! * Use Kernel#warn uplevel argument for nicer warnings. (byroot) * 5 bug fixes: * Cleaned up option aliasing a tad. * Removed obsolete conditional for prerecord * Removed obsolete guards around Warning. * Removed obsolete version guards for pattern matching assertions. * Switched all internal requires to require_relative.

1 0