[ojproductions]

What does this PR do?

dont pin the tracer version. Allow minor version upgrades

Motivation

Testing Guidelines

Additional Notes

Types of changes

• Bug fix
• New feature
• Breaking change
• Misc (docs, refactoring, dependency upgrade, etc.)

Check all that apply

• This PR's description is comprehensive
• This PR contains breaking changes that are documented in the description
• This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
• This PR impacts documentation, and it has been updated (or a ticket has been logged)
• This PR's changes are covered by the automated tests
• This PR collects user input/sensitive content into Datadog

[datadog-datadog-prod-us1]

Automatic tracer upgrades will fail integration checks because the log snapshots still require version 2.46.0. The existing normalization pipeline preserves this field, so even a patch-version change produces a mismatch.

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit e65916d}

[datadog-datadog-prod-us1]

Normalize the tracer version before allowing automatic upgrades

When an automatic upgrade selects a tracer version other than 2.46.0, integration checks fail because all log snapshots require that exact CORE configuration version. The normalization pipeline leaves this field untouched; changing only the version to 2.46.1 reproduces the mismatch. Normalize the field and regenerate the affected snapshots so compatible upgrades can pass.

React: 👍 useful · 👎 wrong · 😕 unclear · 👀 right, but not acting on it

What each reaction means

• 👍 Useful: correct, and you're fixing it or will.
• 👎 Wrong: the finding is incorrect, for example the bug can't happen or the code was misread.
• 😕 Unclear: you can't tell what it means or why it matters.
• 👀 Right, not acting: correct, but intended, out of scope for this PR, a known risk, or too minor.

_{🤖 Bits Code Review · Open Bits AI session}

[joeyzhao2018]

+1 just add some normalizer for the version number