chore(deps): bump libdatadog to 48da0d8#135
Merged
Merged
Conversation
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.
Lewis-E
approved these changes
Jun 10, 2026
Contributor
There was a problem hiding this comment.
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 crateCargo.tomlfiles from0a3304cto48da0d8. - Regenerated
Cargo.lockto reflect the newlibdd-*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
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Bumps
libdatadogrev across all crates from0a3304cto48da0d8.Motivation
The
datadog-lambda-extensionbottlecap binary bumped tolibdatadogrev48da0d8in DataDog/datadog-lambda-extension#1244 for the client-computed header fix. Bottlecap is preparing to consumedatadog-agent-configas 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
libdatadogrev. Thedatadog-agent-configAPI exposeslibdd_trace_obfuscation::replacer::ReplaceRule(viaapm_replace_tags) andlibdd_trace_utilshelpers 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— cleancargo test -p datadog-agent-config— all 71 tests pass