Skip to content

Prepare Ruby 3 support

Matthias Käppler requested to merge 336754-ruby3-prep into master

What does this MR do?

See #336754 (closed)

We are preparing GitLab to run on Ruby 3. This is a much bigger change than past upgrades, due to several breaking changes in the Ruby stdlib APIs, so we are making an effort to prepare the code base step-wise to not break once we flip the switch.

This MR contains a random assortment of backwards-compatible fixes that were required to make several build jobs in our experimental Ruby 3 branch turn green. Breaking these out will solidify the code base prior to making the switch. What this MR does not do is actually make Ruby 3 the default Ruby. That will happen at a later time.

We already try to catch issues in master that we know will become errors in Ruby 3 (via deprecation_toolkit), but this does not cover all such issues (since some are hard to detect and are not issuing deprecation warnings in Ruby 2.7) and also does not cover all code (just specs, but not for instance rake tasks.)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Edited by Matthias Käppler

Merge request reports