[updatecli] update elastic stack version for testing 8.19.8-f0b3abbb

[github-actions]

Bump elastic-stack to latest snapshot version

Update snapshot.yml

1 file(s) updated with "$1:8.19.8-f0b3abbb-SNAPSHOT": * testing/environments/snapshot.yml

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[mergify]

Automatically approving mergify

[mergify]

Merge Queue Status

🚫 The pull request has left the queue (rule: default)

This pull request spent 48 minutes 28 seconds in the queue, including 48 minutes 16 seconds waiting for CI.
The checks were run on draft #47768.

Required conditions to merge

• check-success=buildkite/beats
• any of [🛡 GitHub branch protection]:
  • check-neutral = buildkite/beats
  • check-skipped = buildkite/beats
  • check-success = buildkite/beats
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [updatecli] update elastic stack version for testing 8.19.8-f0b3abbb #47751
• #approved-reviews-by >= 1 [🛡 GitHub repository ruleset rule]
  • [updatecli] update elastic stack version for testing 8.19.8-f0b3abbb #47751
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [updatecli] update elastic stack version for testing 8.19.8-f0b3abbb #47751
• #changes-requested-reviews-by = 0 [🛡 GitHub repository ruleset rule]
  • [updatecli] update elastic stack version for testing 8.19.8-f0b3abbb #47751
• check-success=CLA
• any of [🛡 GitHub branch protection]:
  • check-success = CLA
  • check-neutral = CLA
  • check-skipped = CLA
• any of [🛡 GitHub branch protection]:
  • check-success = buildkite/docs-build-pr
  • check-neutral = buildkite/docs-build-pr
  • check-skipped = buildkite/docs-build-pr

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• ❌ buildkite/beats

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, 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 requeue comment.