deps(example-python): bump ddtrace from 4.10.1 to 4.12.2 in /examples/single_service/src/python-project - #210
Conversation
Bumps [ddtrace](https://github.com/DataDog/dd-trace-py) from 4.10.1 to 4.12.2. - [Release notes](https://github.com/DataDog/dd-trace-py/releases) - [Changelog](https://github.com/DataDog/dd-trace-py/blob/main/CHANGELOG.md) - [Commits](DataDog/dd-trace-py@v4.10.1...v4.12.2) --- updated-dependencies: - dependency-name: ddtrace dependency-version: 4.12.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
There was a problem hiding this comment.
More details
The ddtrace 4.12.2 lockfile resolves with hash checking, imports successfully on Python 3.12, and the example's unittest and pytest paths pass in the available non-Bazel environment. The Bazel targets were not runnable because the sandbox could not access the Bazel Central Registry; no diff-specific behavioral regression was reproduced.
📊 Validated against 4 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 50bdd5f · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
Bumps ddtrace from 4.10.1 to 4.12.2.
Release notes
Sourced from ddtrace's releases.
... (truncated)
Commits
69ecf2dfix(aws_durable_execution_sdk_python): [SVLS-9168] handle FAILED checkpoints ...f1b2b87chore: bump version to 4.12.2 (#19413)ddb7608chore(version): set version to 4.12.1 (#19392)7599b6dchore: raise RSS SLO for tracing-profiling-enabled scenario [backport 4.12] (...e20e14bfix(llmobs): coerce None tool-call arguments in openai streamed chunk reconst...31503e2fix(llmobs): surface OpenRouter BYOK upstream cost [backport 4.12] (#19367)845f8cffix(native): run shutdown in thread in uwsgi [backport 4.12] (#19345)0298937fix(iast): handle literal evidence markers in modulo propagation [backport 4....361a9fachore(iast): preserve propagation during source suppression [backport 4.12] (...357169afix(ci_visibility): add ITR correlation ID [backport 4.12] (#19241)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)