feat: add ruby 3.1 ci pipeline for tests #418
Conversation
saadyousafarbi
force-pushed
the
saad/INF-1008
branch
2 times, most recently
from
6b1f02e
to
52c4fdb
Compare
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #418 +/- ##
=======================================
Coverage 96.14% 96.14%
=======================================
Files 58 58
Lines 4562 4562
=======================================
Hits 4386 4386
Misses 176 176 ☔ View full report in Codecov by Sentry. |
saadyousafarbi
force-pushed
the
saad/INF-1008
branch
2 times, most recently
from
4946f2f
to
94032f2
Compare
saadyousafarbi
force-pushed
the
saad/INF-1008
branch
from
94032f2
to
bcdfc8c
Compare
saadyousafarbi
force-pushed
the
saad/INF-1008
branch
from
bcdfc8c
to
dc55d81
Compare
| @@ -13,12 +13,15 @@ jobs: | |||
| runs-on: ubuntu-20.04 | |||
| strategy: | |||
| matrix: | |||
| ruby-version: ['3.0.4'] | |||
| ruby-version: ['3.0.4', '3.1.0'] | |||
| mongodb-version: ['4.2.14'] | |||
There was a problem hiding this comment.
Do we still need to support both?
I think we need to remove 3.0.4 and regenerate Gemfile.lock ( currently generated for Ruby 2) note currenlty we have Gemfile.lock ( currently generated for Ruby 2) and Gemfile3.lock (Currenlty For ruby 3..0.4) I think we longer need to have both, unless this still support Ruby 2 and we need to regeerate one of them for 3.0.1
There was a problem hiding this comment.
Hi @ghassanmas
We do not need to support both. We will have a cleanup of the Gemfile after the 3.1.0 upgrade work is complete and tested.
Then we will have a single Gemfile for ruby 3.1.0, and single CI for 3.1.0. There will be a followup PR for that!
|
Just want to notify everybody about this PR. Let's complete it and backport to quince. |
|
Do we plan to move forward to Ruby 3.1? |
|
Closed because of this - #426 |
INF-1008
Description
Add Ruby 3.1 CI test pipeline.