merge queue: embarking 7.17 (1932e57) and #18878 together

[mergify]

✨ Pull request #18878 which was ahead in the queue has been dequeued (for the following reason: pull request merged manually). ✨

Branch 7.17 (1932e57) and #18878 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #18878.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default for merge:

• check-success=CLA
• check-success=lint
• check-success=system-test
• check-success=test (macos-latest)
• check-success=test (windows-2025)
• any of [🛡 GitHub branch protection]:
  • check-neutral = CLA
  • check-skipped = CLA
  • check-success = CLA
• any of [🛡 GitHub branch protection]:
  • check-neutral = go-system-tests
  • check-skipped = go-system-tests
  • check-success = go-system-tests
• any of [🛡 GitHub branch protection]:
  • check-neutral = lint
  • check-skipped = lint
  • check-success = lint
• any of [🛡 GitHub branch protection]:
  • check-neutral = python-system-tests
  • check-skipped = python-system-tests
  • check-success = python-system-tests
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/docs-build-pr
  • check-skipped = buildkite/docs-build-pr
  • check-success = buildkite/docs-build-pr
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878

Required conditions to stay in the queue:

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [updatecli] Update to elastic/beats@601d00f8e800 #18878
• any of [🛡 GitHub branch protection]:
  • check-success = CLA
  • check-neutral = CLA
  • check-skipped = CLA
• any of [🛡 GitHub branch protection]:
  • check-success = go-system-tests
  • check-neutral = go-system-tests
  • check-skipped = go-system-tests
• any of [🛡 GitHub branch protection]:
  • check-success = lint
  • check-neutral = lint
  • check-skipped = lint
• any of [🛡 GitHub branch protection]:
  • check-success = python-system-tests
  • check-neutral = python-system-tests
  • check-skipped = python-system-tests
• any of [🛡 GitHub branch protection]:
  • check-success = buildkite/docs-build-pr
  • check-neutral = buildkite/docs-build-pr
  • check-skipped = buildkite/docs-build-pr

---
checking_base_sha: 1932e5740f5e3b9987d1625bca2045238ff122d9
previous_failed_batches: []
pull_requests:
  - number: 18878
...

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)