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.72
botocore	1.43.67	1.43.72
clickhouse-connect	1.6.0	1.7.1
orjson	3.11.9	3.12.0

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

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

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

[datadog-datadog-prod-us1-2]

🎉 All green!

🧪 All tests passed

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

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: 0 selected, 0 skipped (of 0 test tasks)
Publish tasks:   1 (always emitted)
Diff (17 files):
  agent_requirements.in
  amazon_msk/changelog.d/24869.added
  amazon_msk/pyproject.toml
  clickhouse/changelog.d/24869.added
  clickhouse/pyproject.toml
  datadog_checks_base/changelog.d/24869.added
  datadog_checks_base/pyproject.toml
  do_query_actions/changelog.d/24869.added
  do_query_actions/pyproject.toml
  kafka_consumer/changelog.d/24869.added
  kafka_consumer/pyproject.toml
  mysql/changelog.d/24869.added
  mysql/pyproject.toml
  postgres/changelog.d/24869.added
  postgres/pyproject.toml
  riakcs/changelog.d/24869.added
  riakcs/pyproject.toml

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

Learn more about CI impact filtering

[datadog-datadog-prod-us1-2]

All eight dependency changelog fragments use PR 24869 instead of 24877. Repository validation rejects that mismatch, and generated release notes would otherwise link these updates to the unrelated Linux proc FIPS change.

_{Open Bits AI session}

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

[datadog-datadog-prod-us1-2]

Use this PR number for changelog fragments

Changelog validation blocks this PR, and bypassing it would publish dependency release notes linked to an unrelated change.

Assertion details

• Input: Run repository PR validation for PR 24877 or generate a release changelog from these fragments.
• Expected: Rename all eight new fragments from 24869.added to 24877.added and terminate each description with a period, as required by the repository changelog rules. This is a multi-file rename, so an inline suggestion cannot provide the complete fix.
• Actual: Every new fragment is named 24869.added, although 24869 is the already-merged Linux proc FIPS PR. The repository validator explicitly rejects fragment numbers that differ from the current PR, and towncrier uses the filename number to generate the PR link.

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

[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-datadog-prod-us1-2]

More details

The bumped libraries are consumed through narrow, established APIs: ClickHouse connection/query operations, boto3 session/client calls, and orjson dumps/loads wrappers. Resolution files consistently carry the same dependency changes across all five supported platforms.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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