[mhdatie]

Backport #13031 to release/v1.68.x

Now that 1.68.0 is out, I want to verify the fix using the testing steps from the PR. This is safe to keep and easy to revert if needed.

Expected Result
On the next build / patch release, the artifact uploaded to internal S3 should contain the correct patch version bump rather than a minor bump.

---

Output from Gitlab after merging this PR (before and after):

• On release/v1.67.x : dd-java-agent-1.68.0-SNAPSHOT.jar (incorrect)
• On release/v1.68.x : dd-java-agent-1.68.1-SNAPSHOT.jar ✅

The S3 jars: I downloaded both and read them with unzip -p, without running them.

S3 path	Last modified (UTC)	dd-java-agent.version	Manifest Implementation-Version
dd-trace-java-builds/147812303/dd-java-agent.jar	Oct 27, 13:36:50	1.68.1-SNAPSHOT~6dbf51db52	1.68.1-SNAPSHOT
dd-trace-java-builds/release/v1.68.x/dd-java-agent.jar	Oct 27, 13:36:47	1.68.1-SNAPSHOT~6dbf51db52	1.68.1-SNAPSHOT

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-27T12:15:34.009953Z	a7f10c0	PR opened
🔒 Security Review	✅ Completed 2026-10-27T12:17:33.920193Z	a7f10c0	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[datadog-prod-us1-4]

More details

The detached-HEAD fallback restores release-branch patch numbering through CI_COMMIT_BRANCH while preserving attached-branch and tag version selection.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit a7f10c0}

[datadog-prod-us1-4]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 59.99% (-0.00%)

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

[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	14.01 s	13.98 s	[-0.6%; +1.0%] (no difference)
startup:insecure-bank:tracing:Agent	12.90 s	12.90 s	[-0.7%; +0.7%] (no difference)
startup:petclinic:appsec:Agent	16.61 s	16.86 s	[-5.7%; +2.8%] (no difference)
startup:petclinic:iast:Agent	16.78 s	16.59 s	[-3.0%; +5.3%] (no difference)
startup:petclinic:profiling:Agent	16.26 s	16.65 s	[-6.5%; +1.7%] (no difference)
startup:petclinic:sca:Agent	16.98 s	16.38 s	[-0.7%; +8.0%] (no difference)
startup:petclinic:tracing:Agent	16.12 s	16.16 s	[-1.1%; +0.7%] (no difference)

Commit: a7f10c08 · 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.