Repository navigation
merge queue: merged #22398: [8.19] (backport #22390) fix flaky test TestApprovedMetrics - #22403
mergify[bot] wants to merge 2 commits into
Conversation
🤖 GitHub commentsJust comment with:
|
Dependency Update AnalysisSummary: This PR bumps Elastic Stack snapshot pins from Elastic Stack snapshot pins
|
| Check | Result |
|---|---|
| Breaking changes | ✅ None found in repository usage patterns |
| Testable in PR | ✅/ci.yml runs on pull_request/merge_group and executes system-test + system-test-fips with docker compose up; k8s stack manifests are infra config and not directly exercised by default PR jobs |
Changelog highlights (vOLD → vNEW)
Upstream release-note bodies for build IDs 12af652c → 39e70cc6 were not available from local metadata. The update source is .ci/updatecli/bump-elastic-stack-snapshot.yml, which tracks latest snapshot build IDs from artifacts-api/snapshots/<branch>.json.
CVE-focused assessment: no explicit CVE/GHSA entries were available for these snapshot build IDs. This PR only changes external stack image/version pins used for test/infra; it does not modify application authn/authz, parsing, crypto, or privilege logic in this repo.
Usage in this repository
- Updated pins:
docker-compose.yml(elasticsearch-wolfi,kibana-wolfi,metricbeatimages)testing/infra/k8s/base/stack/{apm-server,elasticsearch,kibana}.yaml(spec.version)
- Consuming paths:
systemtest/containers.gostarts stack viadocker compose -f ../docker-compose.ymlsystemtest/cmd/buildapm/main.goreadsdocker-compose.ymlto derive stack tagscript/check_docker_compose.shvalidates snapshot tag currency
- CI execution context:
.github/workflows/ci.yml(on: pull_request, merge_group) runssystem-testandsystem-test-fips, includingdocker compose up -d.
Compatibility assessment
- No repo code/API contract changes accompany this bump; only snapshot identifiers changed.
- Version family remains
8.19.25(build-id refresh), which lowers compatibility risk versus major/minor jumps. - Blast radius is bounded to test/CI/infra stack behavior; production apm-server module dependencies are unchanged.
Labels Applied
oblt-aw/ai/merge-ready— low-to-moderate risk, no breaking usage found, and CI/dev-infra scoped dependency bump with PR-context system-test coverage.
What is this? | From workflow: Observability Agentic Workflow — Pull Request
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.
💚 Build Succeeded
|
Note
This is a merge queue draft opened by Mergify. Its pull request has merged, and nobody needs to act on it.
Mergify opened it for batch recursive-bourguignon-mjppm7 of the
defaultqueue, to test #22398 before it merged into8.19.🎉 What landed
Mergify merged its pull request into
8.19, then closed this draft:62b62f4This draft's code was built in this order:
8.19at6cbd077Metadata for CI tooling, read by
mergify ciRequired conditions of queue rule
defaultfor mergecheck-success=CLAcheck-success=lintcheck-success=system-testcheck-success=test (macos-latest)github-review-approved[🛡 GitHub branch protection]github-review-approved[🛡 GitHub repository ruleset rule[org] Require a PR for Renovate]github-review-approved[🛡 GitHub repository ruleset rule[org] Require a PR]check-success=test (windows-2025)check-success=test (windows-latest)check-success = CLAcheck-neutral = CLAcheck-skipped = CLAcheck-success = lintcheck-neutral = lintcheck-skipped = lintcheck-success = buildkite/docs-build-prcheck-neutral = buildkite/docs-build-prcheck-skipped = buildkite/docs-build-prRequired conditions to stay in the queue
github-review-approved[🛡 GitHub branch protection]github-review-approved[🛡 GitHub repository ruleset rule[org] Require a PR for Renovate]github-review-approved[🛡 GitHub repository ruleset rule[org] Require a PR]check-success = CLAcheck-neutral = CLAcheck-skipped = CLAcheck-success = lintcheck-neutral = lintcheck-skipped = lintcheck-success = buildkite/docs-build-prcheck-neutral = buildkite/docs-build-prcheck-skipped = buildkite/docs-build-pr