[kuahyeow]

Article author here, and also GitLab team member.

If you peek into the source code, I was actually inspired by the ruby-warning gem, and have directly credited it (https://gitlab.com/search?group_id=9970&project_id=278964&re...) :)

Also in Ruby 2.7.2, these warnings that were introduced in 2.7.0 were suppressed by default after feedback from the community.

One thing to note is that because these warnings are runtime, you really need a very comprehensive test suite to find them all. Even then logging such warnings when running in production is probably a good idea.

Agree the Ruby 2.7 => 3.0 change has been handled quite well by the core Ruby team. The kwargs warning is one part of the larger effort to get GitLab onto Ruby 3.0. You can follow along at https://gitlab.com/groups/gitlab-org/-/epics/5149.