[updatecli] Bump elastic stack version to 9.2.2-b263b2b4

[elastic-observability-automation]

What

Bump elastic stack version to 9.2.2-b263b2b4

---

Bump elastic-stack to latest snapshot version

Update k8s stack yaml files

3 file(s) updated with "version: 9.2.2-b263b2b4-SNAPSHOT": * testing/infra/k8s/base/stack/apm-server.yaml * testing/infra/k8s/base/stack/elasticsearch.yaml * testing/infra/k8s/base/stack/kibana.yaml

Update docker-compose.yml

1 file(s) updated with "$1:9.2.2-b263b2b4-SNAPSHOT": * docker-compose.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!

[github-actions]

🤖 GitHub comments

Just comment with:

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

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ system-test

You can check the last failing draft PR here: #19573.

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.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ system-test

You can check the last failing draft PR here: #19582.

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.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ system-test

You can check the last failing draft PR here: #19591.

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.

[mergify]

This pull request has been removed from the queue for the following reason: checks failed.

The merge conditions cannot be satisfied due to failing checks:

• ❌ system-test

You can check the last failing draft PR here: #19595.

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.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 3046184

History

• 💚 Build #7328 succeeded d736362
• 💚 Build #7307 succeeded b03578e
• 💚 Build #7284 succeeded ce3d2f2