Release 0.54.0

[StephenWakely]

What does this PR do?

Prepares the 0.54.0 release: adds the CHANGELOG entry and bumps datadog/version.py. Per RELEASING.md, this should not be merged yet until it's reviewed.

Description of the Change

Three PRs have merged to master since v0.53.0, all labelled changelog/Changed:

• #979 — Retry sending a DogStatsD packet over UDS if the connection drops (opt-in via socket_connect_timeout).
• #986 — Background sender queue now evicts the oldest queued payload when full and expires stale, non-replay-safe payloads.
• #987 — socket_connect_timeout replaced by boolean socket_connect_retry; stop()/wait_for_pending() gain a timeout parameter.

Note: an earlier release attempt for this version, #982, was closed because shutting down the client with a long connect timeout and a full queue could block for a very long time (once per queued item) if the Agent wasn't reachable. That is exactly what #986/#987 fix: a single bounded deadline governs the whole shutdown now, regardless of queue size, and a payload stuck retrying is dropped (and accounted for) rather than blocking indefinitely. #979's changelog entry was missed when #986/#987 were prepared -- it's included here.

Verification Process

• python -m build succeeds; the built wheel installs cleanly into a fresh venv and reports __version__ == "0.54.0".
• flake8 datadog and mypy datadog both clean.
• pytest tests/unit (286 passed, 1 skipped) and pytest tests/unit/dogstatsd (166 passed) -- the 45 failures present in both runs are pre-existing/environment-specific (unrelated container-ID tag injection in this sandbox) and are identical with or without this change.
• Extensive property-based/fuzz testing this session (SenderQueue.close(), the shutdown deadline, the producer/stop race, retry-abandon accounting) against master with real concurrent threads found zero bugs after two initial test-authoring mistakes were corrected.
• No other file references the old 0.53.0 version string.

Additional Notes

Per RELEASING.md, after this merges: create the GitHub release/tag (triggers the PyPI publish workflow), confirm the release lands on PyPI, then open a follow-up PR bumping datadog/version.py to a dev version (e.g. 0.54.1.dev). That last step appears to have been skipped after v0.53.0, since master was left at a flat 0.53.0 -- worth doing this time.

Release Notes

• [Changed] Retry sending a DogStatsD packet over UDS if the connection drops (opt-in via socket_connect_timeout). See #979.
• [Changed] DogStatsD background sender queue now evicts the oldest queued payloads when full, and drops stale non-replay-safe payloads. See #986.
• [Changed] Replace socket_connect_timeout with boolean socket_connect_retry; stop()/wait_for_pending() gain a timeout parameter. See #987.

[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-09-22T17:01:03.859020Z	5c5db2e	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.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5c5db2e2f6

ℹ️ 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".

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

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".