Skip to content

merge queue: merged #22382: [9.5] (backport #22375) bump apm-data to v1.23.0 - #22388

Closed
mergify[bot] wants to merge 4 commits into
9.5from
mergify/merge-queue/287d454379
Closed

merge queue: merged #22382: [9.5] (backport #22375) bump apm-data to v1.23.0#22388
mergify[bot] wants to merge 4 commits into
9.5from
mergify/merge-queue/287d454379

Conversation

@mergify

@mergify mergify Bot commented Nov 5, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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 tight-ganache-7odvt1 of the default queue, to test #22382 before it merged into 9.5.

🎉 What landed

Mergify merged its pull request into 9.5, then closed this draft:

This draft's code was built in this order:

  1. 9.5 at 8a36bad
  2. #22382, the pull request of this batch
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 8a36bad95d481c3e442b01b167cd65e6f876c5ab
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 22382
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
Required conditions to stay in the queue

aelnahas and others added 4 commits November 5, 2026 16:12
@aelnahas @mergify
bump apm-data to v1.23.0 (#22375)
5e61259 
* bump apm-data to v1.23.0

* update NOTICE.txt and NOTICE-fips.txt for apm-data v1.23.0 bump

* fix ci lint and NOTICE-fips.txt

(cherry picked from commit 378a4a7)

# Conflicts:
#	go.mod
@aelnahas
Potential fix for pull request finding 'Resolve go.mod conflict marke…
349e0dc 
…rs to restore Go builds'

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
@aelnahas
run go mod tidy
ec3cbd1
@mergify @mergify-commit-signer
Merge of #22382
d476f26
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

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

@mergify mergify Bot mentioned this pull request Nov 5, 2026
Merged
2 tasks
@elastic-vault-github-plugin-prod

elastic-vault-github-plugin-prod Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Dependency Update Analysis

Summary: This PR updates Go dependencies via go mod tidy (github.com/elastic/apm-data v1.22.2 → v1.23.0, plus indirect go-elasticsearch and opentelemetry-lib bumps). Overall risk is low-to-moderate with no repo-impacting breaking changes found.

Dependency 1: github.com/elastic/apm-data v1.22.2 → v1.23.0

Ecosystem: Go

Check Result
Breaking changes ✅ None found for consumed packages (input/*, model/modelpb, model/modeljson, modelprocessor)
Testable in PR ✅ Yes — repo CI includes pull_request workflows (e.g. .github/workflows/ci.yml)
Changelog highlights (v1.22.2 → v1.23.0)

Release notes show dependency updates and semconv v1.33.0 support; no explicit breaking-change or CVE/GHSA entries in this release note body.
CVE-focused assessment: no newly disclosed vuln IDs in release notes; changes appear to preserve or reduce risk (dependency refresh) without expanding runtime attack surface for current usage.

Usage in this repository

Widely used across ingestion and model pipelines, including internal/beater/*, internal/model/modelprocessor/*, internal/publish/pub.go, and x-pack/apm-server/sampling/* (52 Go files import apm-data packages).

Compatibility assessment

No consumed API removals/renames were identified from release notes or local usage patterns. This is a minor-version bump and remains on the same module major path (v1).

Dependency 2: github.com/elastic/go-elasticsearch/v8 v8.19.6 → v8.19.7

Ecosystem: Go

Check Result
Breaking changes ✅ None found for this bump (8.19.6 → 8.19.7)
Testable in PR ✅ Yes — usage is in integration/system test code exercised by PR CI
Changelog highlights (v8.19.6 → v8.19.7)

Release notes indicate Typed API spec update only; no CVE/GHSA/security-fix entry in this release.
CVE-focused assessment: no reported security regressions in notes; risk profile for current typed API usage is unchanged.

Usage in this repository

Imported in integration/system-test paths (integrationservertest/internal/elasticsearch/client.go, integrationservertest/internal/asserts/*, systemtest/*) using esapi, esutil, and typedapi/*.

Compatibility assessment

Patch-level update on same major path (/v8) with no observed incompatible surface for currently used typed APIs.

Dependency 3: github.com/elastic/opentelemetry-lib v0.39.0 → v0.49.0 (indirect)

Ecosystem: Go

Check Result
Breaking changes ✅ None found affecting this repo directly (no direct imports)
Testable in PR ✅ Yes — transitive impact covered through normal Go build/test CI
Changelog highlights (v0.39.0 → v0.49.0)

Release notes indicate dependency refreshes (OTel collector/tooling bumps); no CVE/GHSA entries listed in the target release notes.
CVE-focused assessment: no explicit vulnerability disclosures in notes; as an indirect dependency, observed risk increase is low.

Usage in this repository

No direct opentelemetry-lib imports were found in this repository; it is pulled transitively.

Compatibility assessment

Because usage is transitive and no direct API consumption exists here, compatibility risk is primarily upstream integration risk and appears contained.

Labels Applied

  • oblt-aw/ai/merge-ready — overall risk is low-to-moderate, no breaking changes affecting current usage were found, and PR CI is available to validate behavior.

What is this? | From workflow: Observability Agentic Workflow — Pull Request

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

@infra-vault-gh-plugin-prod

infra-vault-gh-plugin-prod Bot commented Nov 5, 2026

Copy link
Copy Markdown

💚 Build Succeeded

@mergify mergify Bot changed the title merge queue: checking #22382 on 9.5 (8a36bad) merge queue: merged #22382: [9.5] (backport #22375) bump apm-data to v1.23.0 Nov 5, 2026
@mergify mergify Bot closed this Nov 5, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/287d454379 branch November 5, 2026 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

Copilot code review Copilot
Copilot will automatically review once the pull request is marked ready for review

Assignees

No one assigned

Labels

oblt-aw/ai/merge-ready

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@aelnahas