Skip to content

[9.4](backport #50563) chore: update OTel Collector dependencies to v0.151.0/v1.57.0#50573

Open
mergify[bot] wants to merge 1 commit into9.4from
mergify/bp/9.4/pr-50563
Open

[9.4](backport #50563) chore: update OTel Collector dependencies to v0.151.0/v1.57.0#50573
mergify[bot] wants to merge 1 commit into9.4from
mergify/bp/9.4/pr-50563

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented May 8, 2026

Proposed commit message

Updates the OpenTelemetry Collector dependencies to the current latest versions v0.151.0 and v1.57.0. See changes since v0.150.0/v1.56.0 for Core and Contrib.

Why is it important?

We want to be on the latest version to keep up with latest features and bug fixes.

Checklist

  • [ ] My code follows the style guidelines of this project
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files
  • [ ] I have added tests that prove my fix is effective or that my feature works
  • [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

make mage
(cd auditbeat && mage build)
(cd filebeat && mage build)
(cd metricbeat && mage build)
(cd x-pack/filebeat && mage build)
(cd x-pack/metricbeat && mage build)
```<hr>This is an automatic backport of pull request #50563 done by [Mergify](https://mergify.com).

…50563)

* chore: update OTel Collector dependencies to `v0.151.0`/`v1.57.0`

* go mod tidy

* make notice

(cherry picked from commit 79a0485)

# Conflicts:
#	go.mod
#	go.sum
@mergify mergify Bot requested a review from a team as a code owner May 8, 2026 15:31
@mergify mergify Bot added backport conflicts There is a conflict in the backported pull request labels May 8, 2026
@mergify
Copy link
Copy Markdown
Contributor Author

mergify Bot commented May 8, 2026

Cherry-pick of 79a0485 has failed:

On branch mergify/bp/9.4/pr-50563
Your branch is up to date with 'origin/9.4'.

You are currently cherry-picking commit 79a048584.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   NOTICE.txt

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   go.mod
	both modified:   go.sum

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label May 8, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
  • /test : Run the Buildkite pipeline.

@github-actions github-actions Bot added Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team skip-changelog labels May 8, 2026
@infra-vault-gh-plugin-prod
Copy link
Copy Markdown

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic Bot removed the needs_team Indicates that the issue/PR needs a Team:* label label May 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport conflicts There is a conflict in the backported pull request skip-changelog Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant