chore(deps): update datadog-opentelemetry digest to 0a455ef

[dd-octo-sts]

This PR contains the following updates:

Package	Type	Update	Change
datadog-opentelemetry	dependencies	digest	50bfea8 → 0a455ef

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

[dd-octo-sts]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: bottlecap/Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path bottlecap/Cargo.toml --workspace
info: syncing channel updates for 1.93.1-aarch64-unknown-linux-gnu
info: latest update on 2026-02-12 for version 1.93.1 (01f6ddf75 2026-02-11)
info: downloading 5 components
    Updating crates.io index
warning: spurious network error (3 tries remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
warning: spurious network error (2 tries remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
warning: spurious network error (1 try remaining): [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)
    Updating git repository `https://github.com/DataDog/serverless-components`
From https://github.com/DataDog/serverless-components
 * [new ref]         9daae40afa87f52fad1489f4d7cfd4a579037d2d -> refs/commit/9daae40afa87f52fad1489f4d7cfd4a579037d2d
    Updating git repository `https://github.com/DataDog/dd-trace-rs`
From https://github.com/DataDog/dd-trace-rs
 * [new ref]         0a455eff98accfc42110a2c367c899d333281367 -> refs/commit/0a455eff98accfc42110a2c367c899d333281367
    Updating git repository `https://github.com/DataDog/saluki/`
From https://github.com/DataDog/saluki
 * [new ref]         f863626dbfe3c59bb390985fa6530b0621c2a0a2 -> refs/commit/f863626dbfe3c59bb390985fa6530b0621c2a0a2
error: failed to get `figment` as a dependency of package `bottlecap v0.1.0 (/tmp/renovate/repos/github/DataDog/datadog-lambda-extension/bottlecap)`

Caused by:
  download of config.json failed

Caused by:
  failed to download from `https://index.crates.io/config.json`

Caused by:
  [56] Failure when receiving data from the peer (CONNECT tunnel failed, response 403)

[datadog-official]

✨ Unblock PR with BitsAI

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 15 Pipeline jobs failed

Bottlecap (Rust) | Build All — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Compilation error in src/config/propagation_wrapper.rs: expected TracePropagationStyle, found a different TracePropagationStyle in multiple methods.

Bottlecap (Rust) | Check — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Compilation error in src/config/propagation_wrapper.rs: incompatible type for method 'trace_propagation_style'. Expected 'TracePropagationStyle' from 'datadog_opentelemetry::configuration', but found 'TracePropagationStyle' from 'datadog_agent_config'.

Bottlecap (Rust) | Clippy — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

Compilation error in src/config/propagation_wrapper.rs:24:42: method trace_propagation_style has an incompatible type for trait, expected TracePropagationStyle, found a different TracePropagationStyle.

View all 15 failed jobs.

📋 Copy fix prompt

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Before you start, set up the Datadog software-delivery tooling so you can
query the CI data yourself:

1. Check whether you already have the Datadog software-delivery MCP tools
   (e.g. a `search_datadog_ci_pipeline_events` tool) and the `unblock-pr` skill.
2. If either is missing, STOP and ask me for permission before installing
   anything. Do not install or run anything until I have said yes.
3. Only with my explicit approval, set up the Datadog software-delivery MCP
   server and skills by following:
     https://docs.datadoghq.com/getting_started/software_delivery_mcp_tools/
   then restart so the skill is picked up.
4. If I decline, skip all of the above and work from the context below alone.

Then run /unblock-pr — it will pull the CI data itself. The job context below is what we already know.

If /unblock-pr is not available — because I declined the setup above, or it did not install — work from the context below instead.

Datadog has already classified this failure as caused by changes in this PR.
Take that as given and work the fix:

1. Locate the change. Diff this branch against its base and find the change
   that produces this error. Explain the mechanism, don't just name a file:
     git fetch origin && git diff $(git merge-base origin/main HEAD)...HEAD
2. Reproduce it locally. Run the failing job's command or test before
   proposing anything.
3. Propose the smallest fix that addresses the root cause — not a workaround,
   not a broadened assertion, not a disabled or skipped test.
4. Re-run the same command to confirm, and say exactly what you ran.
5. If the failure turns out to be intermittent rather than deterministic, say
   so plainly instead of "fixing" it — that is a flaky test, and patching it
   hides the problem.

If the right move is to re-run the job rather than change code, use the job
link in the context below. For GitHub Actions: `gh run rerun <run-id> --failed`,
where the run ID is the number after `/runs/` in that URL (not the trailing
number, which is the job ID).

Branch: engraver-auto-version-upgrade/renovate/datadog-opentelemetry-digest

Bottlecap (Rust) | Build All
Commit: 24ead82e38b8d74c56b1fc6fc51f28ad2303cea2
Error (code / build):
Compilation error in src/config/propagation_wrapper.rs: expected `TracePropagationStyle`, found a different `TracePropagationStyle` in multiple methods.
CI job: https://github.com/DataDog/datadog-lambda-extension/actions/runs/34112745705/job/101712483530

Bottlecap (Rust) | Check
Commit: 24ead82e38b8d74c56b1fc6fc51f28ad2303cea2
Error (code / build):
Compilation error in src/config/propagation_wrapper.rs: incompatible type for method 'trace_propagation_style'. Expected 'TracePropagationStyle' from 'datadog_opentelemetry::configuration', but found 'TracePropagationStyle' from 'datadog_agent_config'.
CI job: https://github.com/DataDog/datadog-lambda-extension/actions/runs/34112745705/job/101712483577

Bottlecap (Rust) | Clippy
Commit: 24ead82e38b8d74c56b1fc6fc51f28ad2303cea2
Error (code / build):
Compilation error in src/config/propagation_wrapper.rs:24:42: method `trace_propagation_style` has an incompatible type for trait, expected `TracePropagationStyle`, found a different `TracePropagationStyle`.
CI job: https://github.com/DataDog/datadog-lambda-extension/actions/runs/34112745705/job/101712483688

Plus 2 more failing jobs not shown here.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 24ead82 | Docs | View more details | Give us feedback!}