chore: bump datadog-agent v0.71.0-rc.2 #incident-43109

[jackgopack4]

What does this PR do?

fix go get -u failure first seen here

Motivation

https://app.datadoghq.com/incidents/43109

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• New code is free of linting errors. You can check this by running ./scripts/lint.sh locally.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-09-16 21:01:47

Comparing candidate commit 2683330 in PR branch jackgopack4/bump-datadog-agent-v0.71.0-rc.2 with baseline commit a42a2ba in branch main.

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

scenario:BenchmarkSetTagStringPtr-24

• 🟥 execution_time [+3.621ns; +7.859ns] or [+2.549%; +5.532%]

[datadog-official]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

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

[darccio]

@jackgopack4 This PR can fix the issue, but introducing a lot of changes urgently doesn't feel adequate. The breaking CI pipeline is smoke-tests, so it's quite isolated. Tagging a non-release candidate would fix it.

[jackgopack4]

@darccio thanks, will take a closer look.

[jackgopack4]

go get -u seems to be bumping now to v0.72.0-devel which has a bunch of bad version numbers as dependencies.

[jackgopack4]

yeah it seems like the go get -u upgrades to 72.0-devel when it's on an rc tag, so this won't be sustainable approach

[stevesim101]

Just wondering if there is an ETA on this.........starting to see this impact go project builds at my company that utilize Datadog tracing.

[darccio]

@stevesim101 This issue only impacts your projects if you run go get -u. We advise to prefer targeted upgrades, probably relying on tooling like Dependabot or Renovate.

We understand it's not convenient, but blanket upgrades are discouraged because other dependencies outside of Datadog organization may also introduce breaking changes from time to time: #3779 (comment)