Bump cloudbeat version 9.3 to 9.3.6

[elastic-vault-github-plugin-prod]

No description provided.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-29 12:26 UTC · Rule: default
• ✅ Checks skipped · PR is already up-to-date
• 🚫 Left the queue — 2026-05-29 12:27 UTC · at 4419f424150e0763e79bb173b2cf624dcb0ab557

This pull request spent 47 seconds in the queue, including 4 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • Bump cloudbeat version 9.3 to 9.3.6 #6487
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • Bump cloudbeat version 9.3 to 9.3.6 #6487
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • Bump cloudbeat version 9.3 to 9.3.6 #6487
• any of [🛡 GitHub branch protection]:
  • check-success = Unit Test
  • check-neutral = Unit Test
  • check-skipped = Unit Test
• any of [🛡 GitHub branch protection]:
  • check-success = Lint
  • check-neutral = Lint
  • check-skipped = Lint
• any of [🛡 GitHub branch protection]:
  • check-success = Package Cloudbeat (docker)
  • check-neutral = Package Cloudbeat (docker)
  • check-skipped = Package Cloudbeat (docker)
• any of [🛡 GitHub branch protection]:
  • check-success = Package Cloudbeat (tar.gz)
  • check-neutral = Package Cloudbeat (tar.gz)
  • check-skipped = Package Cloudbeat (tar.gz)

Reason

Pull request #6487 has been dequeued

The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. Repository rule violations found

Changes must be made through the merge queue

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[gsarantid]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-29 13:50 UTC · Rule: default
• ✅ Checks skipped · PR is already up-to-date
• 🚫 Left the queue — 2026-05-29 13:51 UTC · at 4419f424150e0763e79bb173b2cf624dcb0ab557

This pull request spent 35 seconds in the queue, including 5 seconds running CI.

Required conditions to merge

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • Bump cloudbeat version 9.3 to 9.3.6 #6487
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • Bump cloudbeat version 9.3 to 9.3.6 #6487
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • Bump cloudbeat version 9.3 to 9.3.6 #6487
• any of [🛡 GitHub branch protection]:
  • check-success = Unit Test
  • check-neutral = Unit Test
  • check-skipped = Unit Test
• any of [🛡 GitHub branch protection]:
  • check-success = Lint
  • check-neutral = Lint
  • check-skipped = Lint
• any of [🛡 GitHub branch protection]:
  • check-success = Package Cloudbeat (docker)
  • check-neutral = Package Cloudbeat (docker)
  • check-skipped = Package Cloudbeat (docker)
• any of [🛡 GitHub branch protection]:
  • check-success = Package Cloudbeat (tar.gz)
  • check-neutral = Package Cloudbeat (tar.gz)
  • check-skipped = Package Cloudbeat (tar.gz)

Reason

Pull request #6487 has been dequeued

The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. Repository rule violations found

Changes must be made through the merge queue

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.