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.78
botocore	1.43.67	1.43.78
clickhouse-connect	1.6.0	1.7.2
orjson	3.11.9	3.12.0
protobuf	7.35.1	7.36.0

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

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

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 25f0d66f39

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

End dependency changelog entries with periods

This fragment, along with the eight other changelog entries added in this commit, omits the required terminal period. Add a period to every generated Update dependencies entry so the released changelogs follow the repository’s required format.

AGENTS.md reference: AGENTS.md:L208-L211

Useful? React with 👍 / 👎.

[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 (25 files):
  .deps/builder_inputs.toml
  .deps/resolved/linux-aarch64_3.13.txt
  .deps/resolved/linux-x86_64_3.13.txt
  .deps/resolved/macos-aarch64_3.13.txt
  .deps/resolved/macos-x86_64_3.13.txt
  .deps/resolved/windows-x86_64_3.13.txt
  agent_requirements.in
  amazon_msk/changelog.d/24958.added
  amazon_msk/pyproject.toml
  clickhouse/changelog.d/24958.added
  clickhouse/pyproject.toml
  datadog_checks_base/changelog.d/24958.added
  datadog_checks_base/pyproject.toml
  do_query_actions/changelog.d/24958.added
  do_query_actions/pyproject.toml
  kafka_actions/changelog.d/24958.added
  kafka_actions/pyproject.toml
  kafka_consumer/changelog.d/24958.added
  kafka_consumer/pyproject.toml
  mysql/changelog.d/24958.added
  ... and 5 more

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

Learn more about CI impact filtering

[datadog-official]

   

⚠️ Warnings

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

🚦 5 Pipeline jobs failed

PR | test / test (linux, ubuntu-22.04, clickhouse, ClickHouse (py3.13-18), py3.13-18) / ClickHouse (py3.13-18)-py3.13-18 — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

421 tests passed, but 1 test failed with exit code 1 during execution.

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 — 🔧 Needs a code fix, caused by this PR

View more details · View in GitHub Actions

1 test failed out of 421 tests. Exit code 1 indicates an error occurred during execution.

PR | test / check

View more details · View in GitHub Actions

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

View all 5 failed jobs.

📋 Copy fix prompt

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.

Before you start, set up the Datadog software-delivery tooling so you can
query the CI data yourself:

1. Check whether you already have the Datadog software-delivery MCP tools
   (e.g. a `search_datadog_ci_pipeline_events` tool) and the `unblock-pr` skill.
2. If either is missing, STOP and ask me for permission before installing
   anything. Do not install or run anything until I have said yes.
3. Only with my explicit approval, set up the Datadog software-delivery MCP
   server and skills by following:
     https://docs.datadoghq.com/getting_started/software_delivery_mcp_tools/
   then restart so the skill is picked up.
4. If I decline, skip all of the above and work from the context below alone.

Then run /unblock-pr — it will pull the CI data itself. The job context below is what we already know.

If /unblock-pr is not available — because I declined the setup above, or it did not install — work from the context below instead.

Datadog has already classified this failure as caused by changes in this PR.
Take that as given and work the fix:

1. Locate the change. Diff this branch against its base and find the change
   that produces this error. Explain the mechanism, don't just name a file:
     git fetch origin && git diff $(git merge-base origin/master HEAD)...HEAD
2. Reproduce it locally. Run the failing job's command or test before
   proposing anything.
3. Propose the smallest fix that addresses the root cause — not a workaround,
   not a broadened assertion, not a disabled or skipped test.
4. Re-run the same command to confirm, and say exactly what you ran.
5. If the failure turns out to be intermittent rather than deterministic, say
   so plainly instead of "fixing" it — that is a flaky test, and patching it
   hides the problem.

If the right move is to re-run the job rather than change code, use the job
link in the context below. For GitHub Actions: `gh run rerun <run-id> --failed`,
where the run ID is the number after `/runs/` in that URL (not the trailing
number, which is the job ID).

Branch: bot/update-dependencies-1787538395

PR | test / test (linux, ubuntu-22.04, clickhouse, ClickHouse (py3.13-18), py3.13-18) / ClickHouse (py3.13-18)-py3.13-18
Commit: b715222008404323fb69cbbc7ffd44c417a8854f
Error (code / test):
421 tests passed, but 1 test failed with exit code 1 during execution.
CI job: https://github.com/DataDog/integrations-core/actions/runs/32826050463/job/97734314939

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
Commit: b715222008404323fb69cbbc7ffd44c417a8854f
Error (code / test):
1 test failed out of 421 tests. Exit code 1 indicates an error occurred during execution.
CI job: https://github.com/DataDog/integrations-core/actions/runs/32826050463/job/97734315453

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 90.12% (+1.38%)

Useful? React with 👍 / 👎

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

[datadog-official]

The changelog files use PR number 24794, and the dependency resolution files still use the old package versions. These errors stop the required checks.

_{Open Bits AI session}

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

[datadog-official]

Use PR number 24958 in changelog names

The changelog validation check fails and blocks the PR.

Assertion details

• Input: Run the PR validation for PR 24958 with the added 24794.added files.
• Expected: Each new changelog file must use PR number 24958.
• Actual: All nine new files use PR number 24794. The changelog validator compares each file name with PR number 24958 and reports an error.

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

[datadog-official]

Update the generated dependency resolution

The dependency resolution check fails and blocks the merge queue.

Assertion details

• Input: Run the required resolution hash check after the dependency version changes.
• Expected: The dependency workflow must update the resolution hash and all generated resolution files for the new versions.
• Actual: The PR changes a dependency hash input, but .deps/builder_inputs.toml keeps the old hash. The resolved files also keep the old package versions.

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

[datadog-official]

More details

The new dependency versions agree in the project files and generated dependency files. The static review finds no concrete defect.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit b4dff0d · 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