Gemfile.lock checked into repo makes handling diverse Rubies difficult

[petergoldstein]

Ruby version: 2.5-3.1
Rails version: N/A
Sidekiq

I'm trying to add Ruby 3.1 to the CI matrix, but I'm running into issues because the Gemfile.lock is checked into the repo. I'm not entirely sure why.

The problem is that there isn't a single version of Nokogiri that works with Ruby 2.5 and Ruby 3.1. Nokogiri 1.13 is the first version that supports Ruby 3.1 natively. But it requires Ruby 2.6+, so the Ruby 2.5 run fails on bundle install.

Can we remove the Gemfile.lock from the repo? That should fix the issue.

[mperham]

I think I'd rather have 2.5 removed from the matrix. Support for 2.5 is not really important at this point.

[petergoldstein]

Ok, I put up a PR (#5115) but it's not green. Psych changes are a problem for the Delayed Extensions features.

[petergoldstein]

With the latest commit - that shifts the range of tested Rubies to 2.6-3.1 - I'll call this closed.