Skip to content

chore(deps): bump libdatadog to 48da0d8#135

Merged
duncanista merged 1 commit into
mainfrom
chore/bump-libdatadog-48da0d8
Jun 10, 2026
Merged

chore(deps): bump libdatadog to 48da0d8#135
duncanista merged 1 commit into
mainfrom
chore/bump-libdatadog-48da0d8

Conversation

@duncanista

Copy link
Copy Markdown
Contributor

What does this PR do?

Bumps libdatadog rev across all crates from 0a3304c to 48da0d8.

Motivation

The datadog-lambda-extension bottlecap binary bumped to libdatadog rev 48da0d8 in DataDog/datadog-lambda-extension#1244 for the client-computed header fix. Bottlecap is preparing to consume datadog-agent-config as a drop-in replacement for its in-tree config module — see the analysis in the bottlecap migration PR.

For that to work, both repos must point at the same libdatadog rev. The datadog-agent-config API exposes libdd_trace_obfuscation::replacer::ReplaceRule (via apm_replace_tags) and libdd_trace_utils helpers across its boundary, so a rev mismatch causes Cargo to compile two incompatible copies of those types in bottlecap's dependency graph.

Additional Notes

This bump follows the same shape as #127 (bump libdatadog to db05e1f) — 4 Cargo.toml files + Cargo.lock.

Describe how to test/QA your changes

  • cargo check --workspace — clean
  • cargo test -p datadog-agent-config — all 71 tests pass
  • No source changes; rev bump only

Aligns libdatadog rev across all crates with the
datadog-lambda-extension bottlecap binary, which was bumped to this
rev in DataDog/datadog-lambda-extension#1244 for the client-computed
header fix. Required so bottlecap can consume datadog-agent-config
without ending up with two incompatible copies of
libdd-trace-obfuscation::ReplaceRule in its dependency graph.
@duncanista duncanista requested a review from a team as a code owner June 10, 2026 15:33
Copilot AI review requested due to automatic review settings June 10, 2026 15:33
@duncanista duncanista requested a review from a team as a code owner June 10, 2026 15:33
@duncanista duncanista requested review from Lewis-E and jchrostek-dd and removed request for a team June 10, 2026 15:33

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Updates this workspace to use the same libdatadog git revision (48da0d8) across all crates, aligning with the datadog-lambda-extension/bottlecap dependency graph requirements and avoiding duplicate/incompatible libdd-* types at the API boundary.

Changes:

  • Bumped libdd-* git dependencies in 4 crate Cargo.toml files from 0a3304c to 48da0d8.
  • Regenerated Cargo.lock to reflect the new libdd-* package versions and sources.

Reviewed changes

Copilot reviewed 4 out of 5 changed files in this pull request and generated no comments.

Show a summary per file
File Description
crates/datadog-trace-agent/Cargo.toml Updates all libdd-* git rev pins used by the trace agent (including dev-dep libdd-trace-utils).
crates/datadog-serverless-compat/Cargo.toml Updates libdd-trace-utils git rev pin to match the workspace bump.
crates/datadog-metrics-collector/Cargo.toml Updates libdd-common git rev pin (keeping default-features = false).
crates/datadog-agent-config/Cargo.toml Updates libdd-trace-obfuscation and libdd-trace-utils git rev pins for API compatibility.
Cargo.lock Reflects the bumped libdatadog rev and resulting libdd-* version updates.

@duncanista duncanista merged commit aaac1a5 into main Jun 10, 2026
28 checks passed
@duncanista duncanista deleted the chore/bump-libdatadog-48da0d8 branch June 10, 2026 15:59
duncanista added a commit to DataDog/datadog-lambda-extension that referenced this pull request Jun 10, 2026
DataDog/serverless-components#135 merged at aaac1a5d63faf664750a3bf51b50b79449a31625.
The previous pin was the pre-merge branch SHA used during development.
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.

3 participants