Bump hot-shots from 15.0.0 to 16.0.0

[dependabot]

Bumps hot-shots from 15.0.0 to 16.0.0.

Changelog

Sourced from hot-shots's changelog.

16.0.0 (2026-6-8)

• @​bdeitte BREAKING: Add Datadog mode for better parity with the official DogStatsD clients. A new datadog option (explicit true/false, or auto-detected from DD_AGENT_HOST/DD_ENV/other DD_* signals) enables:
  • Origin detection — the container ID is detected from cgroups (Linux only) and sent as |c:. Configurable via originDetection, containerID, and DD_ORIGIN_DETECTION_ENABLED.
  • External Data — read from DD_EXTERNAL_ENV and sent as |e:.
  • Cardinality — a client-wide default (cardinality option or DD_CARDINALITY/DATADOG_CARDINALITY) plus a per metric/event/check cardinality option, sent as |card:.
  • Client telemetry (includeDatadogTelemetry) can be enabled like before. But it also now defaults to on whenever Datadog mode is active — an explicit datadog: true or a DD_* env var. The uds protocol alone does not auto-enable Datadog mode or telemetry. This is a breaking change because clients running in a Datadog environment (e.g. with DD_AGENT_HOST set) will auto-detect Datadog mode and begin emitting the new |c:/|e: wire fields and client telemetry. Opt out with datadog: false, originDetection: false, and/or includeDatadogTelemetry: false. Non-Datadog (StatsD/Telegraf) usage is unaffected.

Commits

• 1b5126e 16.0.0
• 9eb4e8f Changelog update
• 355c565 Merge pull request #320 from bdeitte/datadog-mode
• 2a02cf6 One more small shortening in README
• db7806d Shorten and update initial list of changes
• 20d51b5 docs: add table of contents to README before Example section
• 2f276b1 README cleanup for Datadog and a rearrange
• 4ed277b refactor: extract Datadog setup out of Client constructor
• 8a58ec4 test: disable origin detection in datadog tag/cardinality tests
• 95318f7 docs: fix Datadog mode example + telemetry wording for uds change (review #909)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

This dependency update will be handled internally by our engineering team.