Update dependencies

[dd-octo-sts]

What does this PR do?

Update the dependencies

Dependency Bumps

Package	Old Version	New Version
boto3	1.43.67	1.43.89
botocore	1.43.67	1.43.89
cachetools	7.1.7	7.1.8
clickhouse-connect	1.6.0	1.8.0
cryptography	50.0.0	50.0.1
ddtrace	4.13.2	4.14.0
mmh3	5.2.1	5.3.0
openstacksdk	4.18.0	4.20.0
orjson	3.11.9	3.12.0
protobuf	7.35.1	7.36.1
psycopg	3.3.4	3.3.5
pydantic	2.13.4	2.13.5
simplejson	4.1.1	4.1.2
wrapt	2.3.0	2.4.0

This PR was automatically generated by the following workflow:
https://github.com/DataDog/integrations-core/actions/runs/34074946302

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Changelog entries must be created for modifications to shipped code
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

[github-actions]

Warning

This PR changes Agent dependencies. Do not merge it until the wheels are promoted.

Dependency inputs changed, so the dependency resolution and wheel build workflow runs on this branch. It takes 1.5 to 3 hours and finishes by committing updated lockfiles. The wheels it builds then have to be promoted before the Agent can use them.

Steps to take, in order:

1. Wait for the resolution workflow to finish and commit the lockfiles to this branch.
2. Review the Agent build triggered by that commit (default-pipeline in GitLab), especially static_quality_gate.
3. Get the PR approved.
4. Promote the wheels:

   ddev dep promote https://github.com/DataDog/integrations-core/pull/25125
   

5. Wait for dependency-wheel-promotion to turn green. Only then merge.

Merging before promotion leaves the Agent unable to install the wheels these lockfiles pin. dependency-wheel-promotion is a required check: if it is pending or red, that is intentional. Do not bypass it and do not ask for an admin merge.

Pushing again to this branch invalidates the promotion, so if you push after step 4 you have to promote again.

_{Head commit 34bb038a0d571a669a70157576b62e83593fe4a3. Full process: Dependency Updates. This comment is updated automatically as promotion progresses.}

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   2 (always emitted)
Diff (33 files):
  agent_requirements.in
  amazon_msk/changelog.d/25073.added
  amazon_msk/pyproject.toml
  cisco_aci/changelog.d/25073.added
  cisco_aci/pyproject.toml
  clickhouse/changelog.d/25073.added
  clickhouse/pyproject.toml
  datadog_checks_base/changelog.d/25073.added
  datadog_checks_base/pyproject.toml
  do_query_actions/changelog.d/25073.added
  do_query_actions/pyproject.toml
  http_check/changelog.d/25073.added
  http_check/pyproject.toml
  kafka_actions/changelog.d/25073.added
  kafka_actions/pyproject.toml
  kafka_consumer/changelog.d/25073.added
  kafka_consumer/pyproject.toml
  mongo/changelog.d/25073.added
  mongo/pyproject.toml
  mysql/changelog.d/25073.added
  ... and 13 more

Debug a specific task: evalya plan impact --path <path> --task <task>

Learn more about CI impact filtering

[datadog-prod-us1-3]

All 16 new changelog files use PR number 25073. The release notes therefore link to an unrelated PR instead of PR 25125.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 6f18d1c · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-prod-us1-3]

Use PR 25125 in changelog file names

Users who read the release notes receive an incorrect link for these dependency updates.

Assertion details

• Input: The release process reads the new changelog entries and creates PR links from their file names.
• Expected: The changelog file names must use the current PR number, 25125.
• Actual: All 16 new changelog files use PR number 25073. Release notes link to that unrelated PR.

Was this helpful? React 👍 or 👎
_{🤖 Datadog Autotest · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest · Open Bits AI session}

[datadog-prod-us1-3]

   

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 6 Pipeline jobs failed

PR | test / check

View more details · View in GitHub Actions

Job did not run: blocked by a failed job in an earlier pipeline stage.

PR | test / test (linux, ubuntu-22.04, clickhouse, ClickHouse (py3.13-18), py3.13-18) / ClickHouse (py3.13-18)-py3.13-18

View more details · View in GitHub Actions

HTTP driver received HTTP status 404 during setup, related to unknown identifier: 'readonly' for ClickHouse database connection on URL http://localhost:8123.

PR | test / test-minimum-base-package (linux, ubuntu-22.04, clickhouse, ClickHouse (py3.13-18), py3.13-18) / minimum-base-package-ClickHouse (py3.13-18)-py3.13-18

View more details · View in GitHub Actions

HTTP driver received 404 error from ClickHouse: Unknown identifier: readonly.

View all 6 failed jobs.

🧪 10 Tests failed in 2 jobs

PR | run — ❄️ 8 known flaky tests · 🔄 may pass on retry

View more details · View in GitHub Actions

↳ ❄️ test_check from test_clickhouse.py  

↳ ❄️ test_custom_queries from test_clickhouse.py  

↳ ❄️ test_database_instance_metadata[None] from test_clickhouse.py  

↳ and 5 more — View all

PR All | run — ❌ 2 tests failed

View more details · View in GitHub Actions

❌ test_e2e_check_collects_kubevirt_handler_metrics from test_e2e.py  

Message: HTTPSConnectionPool(host='10.1.0.18', port=41753): Max retries exceeded with url: /healthz (Caused by NewConnectionError("HTTPSConnection(host='10.1.0.18', port=41753): Failed to establish a new connection: [Errno 111] Connection refused"))
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.13/site-packages/urllib3/connection.py", line 204, in _new_conn
    sock = connection.create_connection(
        (self._dns_host, self.port),
    ...<2 lines>...
        socket_options=self.socket_options,
    )
  File "/opt/datadog-agent/embedded/lib/python3.13/site-packages/urllib3/util/connection.py", line 85, in create_connection
    raise err
...

❌ test_e2e_connect_ok from test_e2e.py  

Message: HTTPSConnectionPool(host='10.1.0.18', port=41753): Max retries exceeded with url: /healthz (Caused by NewConnectionError("HTTPSConnection(host='10.1.0.18', port=41753): Failed to establish a new connection: [Errno 111] Connection refused"))
Traceback (most recent call last):
  File "/opt/datadog-agent/embedded/lib/python3.13/site-packages/urllib3/connection.py", line 204, in _new_conn
    sock = connection.create_connection(
        (self._dns_host, self.port),
    ...<2 lines>...
        socket_options=self.socket_options,
    )
  File "/opt/datadog-agent/embedded/lib/python3.13/site-packages/urllib3/util/connection.py", line 85, in create_connection
    raise err
...

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 90.27% (+1.35%)

Useful? React with 👍 / 👎

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

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run

[datadog-prod-us1-3]

More details

The dependency pins and all platform-specific resolved files are consistent. Source inspection shows no actionable regression.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 34bb038 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}