Update instrumentation Gradle dependencies

[dd-octo-sts]

What Does This Do

This PR updates the Gradle dependency locks for instrumentations and their tests.

Motivation

Refresh Gradle dependencies to make sure to test latest versions of dependencies within their supported versions.

Dependency age policy

48h cooldown, updated to the previous version

Too new, so an older eligible version was used instead.

• software.amazon.awssdk:annotations:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:apache-client:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:apache5-client:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:arns:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:auth:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:aws-cbor-protocol:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:aws-core:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:aws-json-protocol:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:aws-query-protocol:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:aws-xml-protocol:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:checksums-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:checksums:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:crt-core:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:dynamodb:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:endpoints-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:eventbridge:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:http-auth-aws-eventstream:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:http-auth-aws:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:http-auth-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:http-auth:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:http-client-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:identity-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:json-utils:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:kinesis:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:metrics-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:netty-nio-client:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:profiles:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:protocol-core:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:regions:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:retries-spi:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:retries:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:s3:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:sdk-core:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:sfn:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:sns:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:third-party-jackson-core:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:third-party-jackson-dataformat-cbor:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:utils-lite:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2
• software.amazon.awssdk:utils:2.48.3 is 16h away from meeting cooldown, updated to 2.48.2

Contributor Checklist

• Update PR title if a code change is needed to support one of those new dependencies

[datadog-prod-us1-6]

More details

This PR updates 450+ gradle.lockfile entries across instrumentation and smoke-test modules with conservative test-dependency version bumps: libsqreen 17.3.0→17.4.0, AWS SDK v2 2.46.21→2.48.2, OpenTelemetry 1.63.0→1.64.0, and minor updates to other test dependencies. All changes are syntactically valid, auto-generated lockfile updates scoped to test configurations only, with no runtime code modifications. No behavioral regressions introduced.

Was this helpful? React 👍 or 👎

_{📊 Validated against 5 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 7a68633 · What is Autotest? · Any feedback? Reach out in #autotest}

[datadog-prod-us1-6]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 79.98% (+22.68%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 7a68633 | Docs | Datadog PR Page | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 7a68633abd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Align Maven Resolver connector with the 2.x stack

When latestDepTest embeds Maven to resolve the sample projects, this lock now moves Resolver API/SPI/impl to 2.0.20 but leaves maven-resolver-connector-basic on 1.9.27 (and transport-http on 1.9.27 later in the file because build.gradle still requests 1.+). Apache's Resolver compatibility notes say integrations should keep API/SPI/impl/connectors/transports on the same version, so MavenCli can fail connector/component loading or artifact resolution before these tests exercise the instrumentation; please align the connector/transport with Resolver 2.x or keep Maven at 3.9.x.

Useful? React with 👍 / 👎.

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	13.93 s	13.88 s	[-0.2%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.93 s	13.01 s	[-1.3%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	16.72 s	16.59 s	[-0.0%; +1.6%] (no difference)
startup:petclinic:iast:Agent	16.39 s	16.91 s	[-7.3%; +1.1%] (no difference)
startup:petclinic:profiling:Agent	16.05 s	16.76 s	[-8.5%; +0.1%] (no difference)
startup:petclinic:sca:Agent	16.91 s	16.61 s	[+0.9%; +2.6%] (maybe worse)
startup:petclinic:tracing:Agent	15.98 s	16.17 s	[-1.7%; -0.5%] (maybe better)

Commit: 7a68633a · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[pr-commenter]

Kafka / producer-benchmark

Parameters

	Baseline	Candidate
baseline_or_candidate	baseline	candidate
git_branch	master	ci/update-gradle-dependencies-instrumentation-20260719
git_commit_date	1784398406	1784438101
git_commit_sha	846103d	7a68633

See matching parameters

	Baseline	Candidate
ci_job_date	1784439098	1784439098
ci_job_id	1872176050	1872176050
ci_pipeline_id	125511727	125511727
cpu_model	Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz
jdkVersion	11.0.25	11.0.25
jmhVersion	1.36	1.36
jvm	/usr/lib/jvm/java-11-openjdk-amd64/bin/java	/usr/lib/jvm/java-11-openjdk-amd64/bin/java
jvmArgs	-Dfile.encoding=UTF-8 -Djava.io.tmpdir=/go/src/github.com/DataDog/apm-reliability/dd-trace-java/platform/src/producer-benchmark/build/tmp/jmh -Duser.country=US -Duser.language=en -Duser.variant	-Dfile.encoding=UTF-8 -Djava.io.tmpdir=/go/src/github.com/DataDog/apm-reliability/dd-trace-java/platform/src/producer-benchmark/build/tmp/jmh -Duser.country=US -Duser.language=en -Duser.variant
vmName	OpenJDK 64-Bit Server VM	OpenJDK 64-Bit Server VM
vmVersion	11.0.25+9-post-Ubuntu-1ubuntu122.04	11.0.25+9-post-Ubuntu-1ubuntu122.04

Summary

Found 0 performance improvements and 0 performance regressions! Performance is the same for 3 metrics, 0 unstable metrics.

See unchanged results

scenario	Δ mean throughput
scenario:not-instrumented/KafkaProduceBenchmark.benchProduce	same
scenario:only-tracing-dsm-disabled-benchmarks/KafkaProduceBenchmark.benchProduce	same
scenario:only-tracing-dsm-enabled-benchmarks/KafkaProduceBenchmark.benchProduce	same