-
-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enforce latest rubygems on CI #2439
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2439 +/- ##
==========================================
+ Coverage 98.09% 98.17% +0.08%
==========================================
Files 126 126
Lines 4723 4723
==========================================
+ Hits 4633 4637 +4
+ Misses 90 86 -4
|
a9a0df5
to
3d7b004
Compare
d38090e
to
cb4492d
Compare
@@ -36,7 +36,7 @@ jobs: | |||
- { ruby_version: 2.6, sidekiq_version: 5.0 } | |||
- { ruby_version: 2.6, sidekiq_version: 6.0 } | |||
- { ruby_version: jruby, sidekiq_version: 5.0 } | |||
- { ruby_version: jruby, sidekiq_version: 6.0 } | |||
- { ruby_version: jruby, sidekiq_version: 6.5 } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With latest rubygems under jruby, bundling sidekiq using 6.0 as the version spec would install sidekiq 6.0.x - and that version actually crashes with Sidekiq[]=
not being defined error.
This makes sure that we use latest rubygems on CI. Without this we're seeing random failures caused by bugs in old Rubygems when bundling may crash with ArgumentError.
I discovered this through #2436 failing like that: https://github.com/getsentry/sentry-ruby/actions/runs/11411361838/job/31767045829?pr=2436#step:4:123
#skip-changelog