Skip to content

[APMSVLS-469] chore(deps): bump libdatadog to a820699 (align bottlecap with serverless-components)#1294

Draft
lucaspimentel wants to merge 1 commit into
mainfrom
lpimentel/bump-libdatadog-a8206994
Draft

[APMSVLS-469] chore(deps): bump libdatadog to a820699 (align bottlecap with serverless-components)#1294
lucaspimentel wants to merge 1 commit into
mainfrom
lpimentel/bump-libdatadog-a8206994

Conversation

@lucaspimentel

@lucaspimentel lucaspimentel commented Jul 2, 2026

Copy link
Copy Markdown
Member

Overview

Aligns bottlecap's libdatadog revision with serverless-components / the Serverless Compat Layer, as a precursor to the APMSVLS-469 error sampler.

  • Bumps all libdd-* pins from 48da0d82 to a820699 (e.g. libdd-trace-utils v6 -> v8, libdd-trace-obfuscation v3 -> v4).
  • Bumps the serverless-components deps (dogstatsd, datadog-fips, datadog-agent-config) from 8ce37eb0 to d05932a5 (current serverless-components main), which pins the same a820699 libdatadog.

Why the two bumps are coupled: datadog-agent-config's public API exposes libdd_trace_obfuscation::ReplaceRule (e.g. Config.apm_replace_tags), which bottlecap consumes. bottlecap and the config crate must therefore resolve to a single libdatadog revision. Mixing revisions puts two incompatible ReplaceRule types in the dependency graph and fails to compile (E0308).

No production source changes. Only bottlecap/Cargo.toml (10 rev bumps) and bottlecap/Cargo.lock.

Why now: the APMSVLS-469 error sampler consumes the new datadog-agent-trace-sampler crate from serverless-components, which lives on a base that pins a820699. Landing this bump first keeps that change focused on the sampler wiring and removes the long-standing bottlecap <-> serverless-components libdatadog drift.

Testing

Verified on a clean worktree off main (only the Cargo bump applied):

  • cargo test --tests: all pass (lib + apm/appsec/logs/metrics integration tests, including the fake-intake trace/stats protobuf roundtrips, so the libdd-trace-protobuf v3.0.2 wire format is compatible).
  • cargo clippy --workspace --all-targets --features default: clean.
  • FIPS build (--no-default-features --features fips) not run locally; relies on CI.

🤖

…ents

Move bottlecap's libdd-* pins from 48da0d82 to a820699, matching the
libdatadog revision used by serverless-components / the Serverless Compat
Layer. Also bump the serverless-components deps (dogstatsd, datadog-fips,
datadog-agent-config) from 8ce37eb0 to d05932a5 (current main), which pins
the same a820699 libdatadog.

The two bumps are coupled: datadog-agent-config's public API exposes
libdd_trace_obfuscation::ReplaceRule, so bottlecap and the config crate
must resolve to a single libdatadog revision. Mixing revisions puts two
incompatible ReplaceRule types in the graph and fails to compile (E0308).

No production source changes. Precursor to the APMSVLS-469 error sampler,
which consumes the datadog-agent-trace-sampler crate from a
serverless-components base that pins a820699.

🤖
@lucaspimentel lucaspimentel changed the title [APMSVLS-469] chore(deps): bump libdatadog to a820699 (align bottlecap with serverless-components) [APMSVLS-469] chore(deps): bump libdatadog to a820699 (align bottlecap with serverless-components) Jul 2, 2026
@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Jul 2, 2026

Copy link
Copy Markdown

Pipelines

Fix all issues with BitsAI

⚠️ Warnings

🚦 4 Pipeline jobs failed

DataDog/datadog-lambda-extension | e2e-test-status (amd64, fips)   View in Datadog   GitLab

DataDog/datadog-lambda-extension | integration-suite: [lmi]   View in Datadog   GitLab

DataDog/datadog-lambda-extension | integration-suite: [on-demand]   View in Datadog   GitLab

View all 4 failed jobs.

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 96ac309 | Docs | Datadog PR Page | Give us feedback!

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.

1 participant