[PROF-13445] Bump minimum version of datadog-ruby_core_source to 3.5.1#5236
Conversation
**What does this PR do?** This PR bumps the minimum version of the datadog-ruby_core_source gem to the latest version (3.5.1), having the usual diff (e.g. #5215 was the previous update). **Motivation:** Doing this bump forces updates to the `datadog` gem to also pull in the latest version of the `datadog-ruby_core_source` gem. This ensures users have the best experience and don't e.g. run into issues because somehow they're running the latest version of the gem with an outdated version of the headers. Specifically version 3.5.1 brings a fix where Ruby 4.0.1 and above would pick the wrong headers to use (DataDog/datadog-ruby_core_source#25) which could result in crashes or incorrect behavior when using the profiler. (It also fixes support for Ruby 4.0.0-preview3 but that's not really very interesting.) **Additional Notes:** This PR is on top of #5234 just to avoid any conflicts when touching the gemfiles but is otherwise completely separate. **How to test the change?** These headers are used by the profiler, so green CI means we're good to go. I've also manually checked with Ruby 4.0.1, 4.0.0 and some other earlier versions to make sure everything is in good shape.
BenchmarksBenchmark execution time: 2026-01-14 14:17:02 Comparing candidate commit 7111ae0 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 44 metrics, 2 unstable metrics. |
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
The expected merge time in
|
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: 7111ae0 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
dd-devflow
Bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: waiting
mergequeue-status: queued
labels
dd-devflow
Bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
**What does this PR do?** This PR bumps the minimum version of the datadog-ruby_core_source gem to the latest version (3.5.2), having the usual diff (e.g. #5236 was the previous update). **Motivation:** Doing this bump forces updates to the datadog gem to also pull in the latest version of the datadog-ruby_core_source gem. This ensures users have the best experience and don't e.g. run into issues because somehow they're running the latest version of the gem with an outdated version of the headers. Specifically version 3.5.2 drops support for the Ruby 4.0.0-preview2 headers, so overall should not impact anyone, while at the same time having a smaller on-disk footprint (DataDog/datadog-ruby_core_source#26). **Additional Notes:** N/A **How to test the change?** Green CI is good!
2 participants
What does this PR do?
This PR bumps the minimum version of the datadog-ruby_core_source gem to the latest version (3.5.1), having the usual diff (e.g. #5215 was the previous update).
Motivation:
Doing this bump forces updates to the
datadoggem to also pull in the latest version of thedatadog-ruby_core_sourcegem. This ensures users have the best experience and don't e.g. run into issues because somehow they're running the latest version of the gem with an outdated version of the headers.Specifically version 3.5.1 brings a fix where Ruby 4.0.1 and above would pick the wrong headers to use
(DataDog/datadog-ruby_core_source#25) which could result in crashes or incorrect behavior when using the profiler.
(It also fixes support for Ruby 4.0.0-preview3 but that's not really very interesting.)
Change log entry
Yes. Bump minimum version of datadog-ruby_core_source to 3.5.1
Additional Notes:
This PR is on top of #5234 just to avoid any conflicts when touching the gemfiles but is otherwise completely separate.
How to test the change?
These headers are used by the profiler, so green CI means we're good to go.
I've also manually checked with Ruby 4.0.1, 4.0.0 and some other earlier versions to make sure everything is in good shape.