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.62
botocore	1.43.40	1.43.62
cachetools	7.1.4	7.1.7
clickhouse-connect	1.4.1	1.6.0
cryptography	48.0.1	50.0.0
kubernetes	35.0.0	36.0.3
prometheus-client	0.25.0	0.26.0
pyopenssl	26.2.0	26.4.0
redis	7.3.0	8.1.0
wrapt	2.2.2	2.3.0

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

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/24750
   

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 c841d578b9f85e5a333c7cf46cc2c5d896d6758c. Full process: Dependency Updates. This comment is updated automatically as promotion progresses.}

[datadog-datadog-us1-prod]

   

⚠️ Warnings

🚦 17 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     

🔧 Fix in code. This looks caused by changes in this PR.

1 failed test. AssertionError: Regex pattern did not match. Expected regex: re.compile('authentication required|operation not permitted', re.IGNORECASE). Actual message: 'HELLO must be called with the client already authenticated.'

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     

🔧 Fix in code. This looks caused by changes in this PR.

1 failed test. AssertionError: Regex pattern did not match: Expected regex: 'authentication required|operation not permitted'; Actual message: 'HELLO must be called with the client already authenticated.'

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     

🔧 Fix in code. This looks caused by changes in this PR.

1 test failed: test_redis_auth_empty_pass. AssertionError: Regex pattern did not match for empty password test.

View all 17 failed jobs.

📋 Copy prompt for your agent

CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Branch: bot/update-dependencies-1785725938

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
Commit: 6b67b663276eb8e75fd228b51efb3083bcdb4111
Error (code / test):
1 failed test. AssertionError: Regex pattern did not match. Expected regex: re.compile('authentication required|operation not permitted', re.IGNORECASE). Actual message: 'HELLO must be called with the client already authenticated.'
CI job: https://github.com/DataDog/integrations-core/actions/runs/30780613327/job/91584420855

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
Commit: 6b67b663276eb8e75fd228b51efb3083bcdb4111
Error (code / test):
1 failed test. AssertionError: Regex pattern did not match: Expected regex: 'authentication required|operation not permitted'; Actual message: 'HELLO must be called with the client already authenticated.'
CI job: https://github.com/DataDog/integrations-core/actions/runs/30780613327/job/91584421105

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
Commit: 6b67b663276eb8e75fd228b51efb3083bcdb4111
Error (code / test):
1 test failed: test_redis_auth_empty_pass. AssertionError: Regex pattern did not match for empty password test.
CI job: https://github.com/DataDog/integrations-core/actions/runs/30780613327/job/91584421113

Plus 7 more failing jobs not shown here.

🧪 17 Tests failed in 2 jobs

PR | run  

test_redis_auth_empty_pass from test_auth.py  

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

❄️ Known flaky: test_redis_auth_ok from test_auth.py  

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

Not introduced in this PR.

View all failed tests

PR All | 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'")
...

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

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

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: c841d57 | 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: c841d578b9

ℹ️ 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]

Rename ClickHouse changelog to a valid type

The ClickHouse dependency bump needs this fragment to satisfy changelog validation, but 24750.1 parses the change type as 1; the PR changelog check rejects any type outside the configured set and release tooling will not categorize this entry. Rename it to 24750.added (or another valid type) so the dependency update has a usable changelog entry.

AGENTS.md reference: AGENTS.md:L187-L203

Useful? React with 👍 / 👎.

[datadog-datadog-us1-prod]

More details

The dependency upgrades were exercised through the highest-risk ClickHouse, Redis, Kueue, and Mongo integration paths without reproducing crashes, API incompatibilities, or incorrect outputs. The Redis 8.1.0 and ClickHouse Connect 1.6.0 APIs used by these checks remain available and compatible with the current callers.

Was this helpful? React 👍 or 👎

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

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