Skip to content

Bump cloudbeat version 9.4 to 9.4.3#6489

Merged
biscout42 merged 1 commit into
9.4from
bump-to-9.4.3
May 29, 2026
Merged

Bump cloudbeat version 9.4 to 9.4.3#6489
biscout42 merged 1 commit into
9.4from
bump-to-9.4.3

Conversation

@elastic-vault-github-plugin-prod
Copy link
Copy Markdown
Contributor

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod Bot commented May 28, 2026

No description provided.

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod Bot requested a review from a team as a code owner May 28, 2026 15:02
@mergify mergify Bot added the queued label May 29, 2026
@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 29, 2026 •
edited
Loading

Merge Queue Status

This pull request spent 18 minutes 32 seconds in the queue, including 17 minutes 30 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • 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 #6489 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.

mergify Bot added a commit that referenced this pull request May 29, 2026
@mergify
Merge of #6489
2572e92
@mergify mergify Bot mentioned this pull request May 29, 2026
Closed
38 tasks
@mergify mergify Bot added dequeued and removed queued labels May 29, 2026
@gsarantid
Copy link
Copy Markdown

gsarantid commented May 29, 2026

@Mergifyio queue

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented May 29, 2026 •
edited
Loading

Merge Queue Status

This pull request spent 18 minutes 49 seconds in the queue, including 17 minutes 41 seconds running CI.

Required conditions to merge
  • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR for Renovate]
  • #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule [org] Require a PR]
  • 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 #6489 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.

@mergify mergify Bot added the queued label May 29, 2026
mergify Bot added a commit that referenced this pull request May 29, 2026
@mergify
Merge of #6489
e4d5516
@mergify mergify Bot mentioned this pull request May 29, 2026
Closed
38 tasks
@biscout42 biscout42 added this pull request to the merge queue May 29, 2026
Merged via the queue into 9.4 with commit c3c4455 May 29, 2026
15 of 16 checks passed
@biscout42 biscout42 deleted the bump-to-9.4.3 branch May 29, 2026 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gsarantid gsarantid gsarantid approved these changes

@biscout42 biscout42 biscout42 approved these changes

Assignees

No one assigned

Labels

backport-skip dequeued

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@gsarantid @biscout42 @cloudsecmachine