-
Notifications
You must be signed in to change notification settings - Fork 373
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
Removing dev and check groups from appraisal groups #4198
Conversation
Thank you for updating Change log entry section 👏 Visited at: 2024-12-06 12:24:55 UTC |
c22b226
to
9ac915d
Compare
2b505ef
to
eea3232
Compare
BenchmarksBenchmark execution time: 2024-12-06 12:52:23 Comparing candidate commit eea3232 in PR branch Found 0 performance improvements and 1 performance regressions! Performance is the same for 30 metrics, 2 unstable metrics. scenario:tracing - Propagation - Trace Context
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4198 +/- ##
==========================================
- Coverage 97.77% 97.75% -0.02%
==========================================
Files 1357 1357
Lines 81941 81940 -1
Branches 4168 4168
==========================================
- Hits 80114 80104 -10
- Misses 1827 1836 +9 ☔ View full report in Codecov by Sentry. |
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.
👍 LGTM
Motivation:
I found
ruby_memcheck
is propagated in Ruby 3.4, because removal list is hardcoded.This means it can easily be forgotten by people due to forgetting them.
What does this PR do?
Exclude all gems from
dev
andcheck
groups. Since gemfile generation is a standalone process, we can even migrateappraisal
gem intodev
group.Maybe this (customize solution )would be a better strategy compared to standalone task with its own dependency from this PR #3918
Change log entry
None.