[NO-TICKET] Upgrade libdatadog dependency to version 26.0.0

[ivoanjo]

What does this PR do?

This PR bumps the libdatadog dependency from version 25.0.1.1.0 to version 26.0.0.1.0.

This new version cleans up the profile exporting API so I've updated our code to match.

Also, this is the first libdatadog version with macOS builds!
(Foreshadowing...)

Motivation:

Adopt latest libdatadog.

Change log entry

Yes. Upgrade libdatadog dependency to version 26.0.0

Additional Notes:

N/A

How to test the change?

Green CI is good, as usual.

[ivoanjo]

Hmm we're hitting the packaging limits, I've ping'd @lloeki for help on that one...

[datadog-datadog-prod-us1]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
• Patch Coverage: 100.00%
• Overall Coverage: 95.15% (-0.01%)

View detailed report

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-02-05 09:53:26

Comparing candidate commit 0413bfb in PR branch ivoanjo/libdatadog-26-ruby with baseline commit 8f4c16d in branch master.

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

scenario:profiling - http_transport

• 🟥 throughput [-2566.266op/s; -2562.501op/s] or [-95.172%; -95.032%]

scenario:profiling - intern_all 1000 repeated strings

• 🟥 throughput [-3998.978op/s; -3907.882op/s] or [-15.295%; -14.946%]

scenario:profiling - stack collector (varying depth)

• 🟥 throughput [-67.878op/s; -67.154op/s] or [-7.059%; -6.984%]

[ivoanjo]

Update: We're investigating a possible bug in the profiling reporting code, I'm moving this to draft for now until we confirm it's all good (or else that we need a libdatadog bugfix release)

[ivoanjo]

Update we're treating DataDog/libdatadog#1492 and DataDog/libdatadog#1493 as blockers to getting this merged

[ivoanjo]

Update:

• I've rebased on top of current master + force pushed to clean up the history (it had gotten a bit dirty from updating the gemfiles)
• revert(profiling): backend does not use MIME libdatadog#1511 is the current blocker for upgrading to latest libdatadog