Update dependencies

[dd-octo-sts]

What does this PR do?

Update the dependencies

Dependency Bumps

Package	Old Version	New Version
boto3	1.43.40	1.43.56
botocore	1.43.40	1.43.56
cachetools	7.1.4	7.1.6
clickhouse-connect	1.4.1	1.6.0
cryptography	48.0.1	49.0.0
kubernetes	35.0.0	36.0.3
prometheus-client	0.25.0	0.26.0
pyopenssl	26.2.0	26.3.0
redis	7.3.0	8.0.1

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

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.

[datadog-datadog-prod-us1]

   

✨ Unblock PR with BitsAI

⚠️ Warnings

🚦 16 Pipeline jobs failed

PR | test / test (linux, ubuntu-22.04, redisdb, Redis (py3.13-6.0), py3.13-6.0) / Redis (py3.13-6.0)-py3.13-6.0     

PR | test / test (linux, ubuntu-22.04, redisdb, Redis (py3.13-7.0), py3.13-7.0) / Redis (py3.13-7.0)-py3.13-7.0     

PR | test / test (linux, ubuntu-22.04, redisdb, Redis (py3.13-8.0), py3.13-8.0) / Redis (py3.13-8.0)-py3.13-8.0     

View all 16 failed jobs.

🧪 20 Tests failed in 2 jobs

PR | run  

test_valid_version_and_critical_certificate_validation_due_to_parsing_error from test_remote.py  

Needed exactly 1 candidates for 'tls.cert_validation', got 0
Expected:
        ServiceCheckStub(check_id=None, name='tls.cert_validation', status=2, tags=['port:443', 'port:443', 'server:valid.mock', 'server:valid.mock', 'server_hostname:valid.mock', 'server_hostname:valid.mock'], hostname=None, message="Unable\\ to\\ parse\\ the\\ certificate:\\ argument\\ 'data':\\ ")
Difference to closest:
        Expected message: Unable\ to\ parse\ the\ certificate:\ argument\ 'data':\ 
        Found Unable to parse the certificate: 'MagicMock' object is not an instance of 'bytes'

Similar submitted:
Score   Most similar
0.93    ServiceCheckStub(check_id='', name='tls.cert_validation', status=2, tags=['port:443', 'port:443', 'server:valid.mock', 'server:valid.mock', 'server_hostname:valid.mock', 'server_hostname:valid.mock'], hostname='', message="Unable to parse the certificate: 'MagicMock' object is not an instance of 'bytes'")
...

PR All | run  

test_redis_auth_empty_pass from test_auth.py  

RetryError[<Future at 0x7fa3c84dee90 state=finished raised ResponseError>]

❄️ Known flaky: test_redis_auth_ok from test_auth.py  

RetryError[<Future at 0x7fa3c84dee90 state=finished raised ResponseError>]

Not introduced in this PR.

View all failed tests

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 89.83% (+1.46%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 98a9955 | Docs | Datadog PR Page | 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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 98a99553bc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Keep redis-py on the RESP2-compatible major

For the Redis 5.0 environment explicitly retained in redisdb/hatch.toml, redis-py 8 enables the RESP3/HELLO connection behavior while Redis 5 predates that command. _get_conn constructs redis.Redis without a protocol override, so the supported Redis 5 check fails during connection setup before collecting metrics. Commit 283cdf26 already reverted this same redis 8 bump because it broke redisdb; retain 7.3 or add compatible protocol handling before upgrading.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Do not repin cryptography 49 for Intel macOS

In the resolve-build-deps.yaml macOS x86_64 target, cryptography 49 has no compatible Intel/universal wheel, so resolution falls back to an sdist build that fails after the workflow removes the OpenSSL/pkg-config build prerequisites. The repository explicitly pinned <49 for this target in commit 560b68ff, and commit 283cdf26 reverted this exact Agent dependency bump after it broke TLS and the macOS x86_64 build; this pin reintroduces that failure.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Avoid the version-36 Kubernetes wheel regression

The previous dependency update (283cdf26) tested Kubernetes 36.0.2 and reverted it because its wheel grew from 1.92 MB to 4.40 MB, adding about 2.48 MB and tripping the Agent static-size quality gate. Moving to the adjacent 36.0.3 release without any corresponding size mitigation reintroduces the same version-36 generated-client payload into the resolve-build-deps.yaml artifacts, preventing the dependency set from passing that gate.

Useful? React with 👍 / 👎.

[datadog-datadog-prod-us1]

More details

The updated ClickHouse, Redis, and Kubernetes client pins preserved connection construction, Redis fallback/error paths, and Kueue API-version fallback behavior in freshly resolved environments. No additional tests recommended: production telemetry is unavailable and the exercised compatibility branches are already covered by deterministic unit scenarios.

Was this helpful? React 👍 or 👎

_{📊 Validated against 336 scenarios · Open Bits AI session}

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