Skip to content

[PROF-13115] Bump minimum datadog-ruby_core_source dependency to 3.4.2#5122

Merged
ivoanjo merged 5 commits intomasterfrom
ivoanjo/prof-13115-bump-ruby-headers
Dec 9, 2025
Merged

[PROF-13115] Bump minimum datadog-ruby_core_source dependency to 3.4.2#5122
ivoanjo merged 5 commits intomasterfrom
ivoanjo/prof-13115-bump-ruby-headers

Conversation

@ivoanjo
Copy link
Member

@ivoanjo ivoanjo commented Dec 9, 2025

What does this PR do?

This PR bumps the minimum version of datadog-ruby_core_source from 3.4.1 to 3.4.2 + removes the workaround we had for Ruby 4.0 in CI.

Motivation:

This makes sure an older version is not accidentally kept around.

Change log entry

Yes. Bump minimum datadog-ruby_core_source dependency to 3.4.2.

Additional Notes:

Once this is merged, we can undo the workaround in DataDog/datadog-ruby_core_source#20 .

How to test the change?

Validate that CI is green!

This reverts commit 83a0969.

No longer needed -- the latest version on rubygems.org now
includes these changes.
…ersion is used

This makes sure an older version is not accidentally kept around.

(This is needed for Ruby 4.0.0-preview2 support)
@ivoanjo ivoanjo requested a review from a team as a code owner December 9, 2025 10:15
@ivoanjo ivoanjo requested a review from a team December 9, 2025 10:16
Copy link
Member

@Strech Strech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍🏼

@datadog-official
Copy link

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
Patch Coverage: 100.00%
Total Coverage: 95.23% (+0.00%)

View detailed report

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: b83696b | Docs | Datadog PR Page | Was this helpful? Give us feedback!

@pr-commenter
Copy link

pr-commenter bot commented Dec 9, 2025

Benchmarks

Benchmark execution time: 2025-12-09 10:55:23

Comparing candidate commit b83696b in PR branch ivoanjo/prof-13115-bump-ruby-headers with baseline commit 49a28d5 in branch master.

Found 3 performance improvements and 1 performance regressions! Performance is the same for 40 metrics, 2 unstable metrics.

scenario:profiling - sample+serialize retain_every=10 heap_samples=false heap_size=false heap_sample_every=1 skip_end_gc=false

  • 🟥 throughput [-0.202op/s; -0.182op/s] or [-7.293%; -6.578%]

scenario:tracing - 100 span trace - no writer

  • 🟩 throughput [+17.938op/s; +18.728op/s] or [+5.920%; +6.181%]

scenario:tracing - Propagation - Trace Context

  • 🟩 throughput [+3188.737op/s; +3296.313op/s] or [+9.352%; +9.667%]

scenario:tracing - Tracing.log_correlation

  • 🟩 throughput [+7415.463op/s; +7706.330op/s] or [+7.413%; +7.704%]

@ivoanjo ivoanjo merged commit 4bae228 into master Dec 9, 2025
565 of 566 checks passed
@ivoanjo ivoanjo deleted the ivoanjo/prof-13115-bump-ruby-headers branch December 9, 2025 12:07
@github-actions github-actions bot added this to the 2.23.0 milestone Dec 9, 2025
ivoanjo added a commit to DataDog/datadog-ruby_core_source that referenced this pull request Dec 9, 2025
…em release"

**What does this PR do?**

This reverts commit 551b5ae from #20.

See #20 for details. In that PR I mentioned:

So to break the loop, let's:

1. omit this test temporarily: ✅ done -> this was #20
2. then we can release this gem: ✅ done ->
   https://github.com/DataDog/datadog-ruby_core_source/actions/runs/20059401843,
   [version 3.4.2 is on rubygems.org](https://rubygems.org/gems/datadog-ruby_core_source/versions/3.4.2)
3. then we can undo the dd-trace-rb pinning: ✅ done ->
   DataDog/dd-trace-rb#5122
4. then we can re-enable the test

This PR is step 4 and gets us back to where we were before the
workaround.

**Motivation:**

Remove workaround now that it's not needed anymore!

**Additional Notes:**

N/A

**How to test the change?**

Validate that Ruby 4.0 + "corruption" test is running in CI and green.
@Strech Strech mentioned this pull request Dec 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants