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.46
botocore	1.43.40	1.43.46
clickhouse-connect	1.4.1	1.4.2
cryptography	48.0.1	49.0.0
kubernetes	35.0.0	36.0.2
pymysql	1.1.2	1.2.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/29220602063

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-prod-us1-3]

   

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 22 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 22 failed jobs.

🧪 3 Tests failed in 1 job

PR All | run  

test_activity_collection[SELECT id, name as name0, name as name1, name as name2, name as name3, name as name4, name as name5, name as name6, name as name7, name as name8, name as name9, name as name10, name as name11, name as name12, name as name13, name as name14, name as name15, name as name16, name as name17, name as name18, name as name19, name as name20, name as name21, name as name22, name as name23, name as name24, name as name25, name as name26, name as name27, name as name28, name as name29, name as name30, name as name31, name as name32, name as name33, name as name34, name as name35, name as name36, name as name37, name as name38, name as name39, name as name40, name as name41, name as name42, name as name43, name as name44, name as name45, name as name46, name as name47, name as name48, name as name49, name as name50, name as name51, name as name52, name as name53, name as name54, name as name55, name as name56, name as name57, name as name58, name as name59, name as name60, name as name61, name as name62, name as name63, name as name64, name as name65, name as name66, name as name67, name as name68, name as name69, name as name70, name as name71, name as name72, name as name73, name as name74, name as name75, name as name76, name as name77, name as name78, name as name79, name as name80, name as name81, name as name82, name as name83, name as name84, name as name85, name as name86, name as name87, name as name88, name as name89, name as name90, name as name91, name as name92, name as name93, name as name94, name as name95, name as name96, name as name97, name as name98, name as name99, name as name100, name as name101, name as name102, name as name103, name as name104, name as name105, name as name106, name as name107, name as name108, name as name109, name as name110, name as name111, name as name112, name as name113, name as name114, name as name115, name as name116, name as name117, name as name118, name as name119, name as name120, name as name121, name as name122, name as name123, name as name124, name as name125, name as name126, name as name127, name as name128, name as name129, name as name130, name as name131, name as name132, name as name133, name as name134, name as name135, name as name136, name as name137, name as name138, name as name139, name as name140, name as name141, name as name142, name as name143, name as name144, name as name145, name as name146, name as name147, name as name148, name as name149, name as name150, name as name151, name as name152, name as name153, name as name154, name as name155, name as name156, name as name157, name as name158, name as name159, name as name160, name as name161, name as name162, name as name163, name as name164, name as name165, name as name166, name as name167, name as name168, name as name169, name as name170, name as name171, name as name172, name as name173, name as name174, name as name175, name as name176, name as name177, name as name178, name as name179, name as name180, name as name181, name as name182, name as name183, name as name184, name as name185, name as name186, name as name187, name as name188, name as name189, name as name190, name as name191, name as name192, name as name193, name as name194, name as name195, name as name196, name as name197, name as name198, name as name199, name as name200, name as name201, name as name202, name as name203, name as name204, name as name205, name as name206, name as name207, name as name208, name as name209, name as name210, name as name211, name as name212, name as name213, name as name214, name as name215, name as name216, name as name217, name as name218, name as name219, name as name220, name as name221, name as name222, name as name223, name as name224, name as name225, name as name226, name as name227, name as name228, name as name229, name as name230, name as name231, name as name232, name as name233, name as name234, name as name235, name as name236, name as name237, name as name238, name as name239, name as name240, name as name241, name as name242, name as name243, name as name244, name as name245, name as name246, name as name247, name as name248, name as name249, name as name250, name as name251, name as name252, name as name253 FROM testdb.users FOR UPDATE-63bd1fd025c7f7fb-truncated-False] from test_query_activity.py  

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

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

View all failed tests

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

🔄 Datadog auto-retried 1 job - 0 passed on retry

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 89.75%

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0a93c7b | Docs | Datadog PR Page | Give us feedback!}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a3d2ec1658

ℹ️ 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 RESP2 for Redis 5

This bump crosses redis-py 8.0, whose maintainers note that clients now use RESP3 by default and that this causes connection failures for Redis <6 or proxies without HELLO support (release note, issue); our Redis check still tests/supports Redis 5.0 in redisdb/hatch.toml and _get_conn constructs redis.Redis(**connection_params) without any protocol=2 override, so Redis 5 users will fail the handshake and report redis.can_connect critical instead of collecting metrics. Please either stay on 7.x or force/expose RESP2 before taking this major version.

Useful? React with 👍 / 👎.

[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