chore: update OTel Collector dependencies to v0.155.0/v1.61.0#51684
Conversation
sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v0\.154.0/\1 v0.155.0/" go.mod sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v1\.60.0/\1 v1.61.0/" go.mod sed -i '' "s/\(github.com\/open-telemetry\/opentelemetry-collector-contrib\/.*\) v0\.154.0/\1 v0.155.0/" go.mod
🤖 GitHub commentsJust comment with:
|
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
v0.155.0/v1.61.0
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughChangesCompact metadata
This PR bumps the Go toolchain version and a broad set of third-party dependencies, including AWS SDK for Go v2 (core and numerous submodules), Sequence Diagram(s)Not applicable — this change is limited to dependency version bumps, build/manifest pin updates, and license notice regeneration. Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
TL;DRThe OTel distro build is failing because the PR bumps the repository OTel dependencies to Remediation
Investigation detailsRoot CauseThis is a dependency/configuration mismatch introduced by the OTel version bump. The PR changes
The Buildkite command also installs an older collector builder: .buildkite/x-pack/pipeline.xpack.otel.yml:58
go install go.opentelemetry.io/collector/cmd/builder@v0.150.0Because the manifest replaces Evidence
VerificationNot run locally; no code changes were made in this read-only CI detective workflow. The failed Buildkite log and PR diff were sufficient to identify the version skew. What is this? | From workflow: PR Buildkite Detective Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. |
|
Big jump from 150 to 155. Thanks for updating it |
|
@Mergifyio backport 9.4 9.3 8.19 |
✅ Backports have been createdDetails
Cherry-pick of 539bc0e has failed: 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
Cherry-pick of 539bc0e has failed: 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
Cherry-pick of 539bc0e has failed: 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 |
…v0.155.0`/`v1.61.0` (#51703) * chore: update OTel Collector dependencies to `v0.155.0`/`v1.61.0` (#51684) * chore: update OTel Collector dependencies to `v0.155.0`/`v1.61.0` sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v0\.154.0/\1 v0.155.0/" go.mod sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v1\.60.0/\1 v1.61.0/" go.mod sed -i '' "s/\(github.com\/open-telemetry\/opentelemetry-collector-contrib\/.*\) v0\.154.0/\1 v0.155.0/" go.mod * go mod tidy && make notice * chore: update distro version (cherry picked from commit 539bc0e) # Conflicts: # NOTICE.txt # go.mod # go.sum * fix: resolve go.mod/go.sum conflicts, run go mod tidy and make notice --------- Co-authored-by: Andrzej Stencel <andrzej.stencel@elastic.co> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
…v0.155.0`/`v1.61.0` (#51702) * chore: update OTel Collector dependencies to `v0.155.0`/`v1.61.0` (#51684) * chore: update OTel Collector dependencies to `v0.155.0`/`v1.61.0` sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v0\.154.0/\1 v0.155.0/" go.mod sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v1\.60.0/\1 v1.61.0/" go.mod sed -i '' "s/\(github.com\/open-telemetry\/opentelemetry-collector-contrib\/.*\) v0\.154.0/\1 v0.155.0/" go.mod * go mod tidy && make notice * chore: update distro version (cherry picked from commit 539bc0e) # Conflicts: # NOTICE.txt # go.mod # go.sum * fix: resolve go.mod conflicts keeping v0.155.0/v1.61.0 versions, run go mod tidy and make notice --------- Co-authored-by: Andrzej Stencel <andrzej.stencel@elastic.co> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
…`v0.155.0`/`v1.61.0` (#51704) * chore: update OTel Collector dependencies to `v0.155.0`/`v1.61.0` (#51684) * chore: update OTel Collector dependencies to `v0.155.0`/`v1.61.0` sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v0\.154.0/\1 v0.155.0/" go.mod sed -i '' "s/\(go\.opentelemetry\.io\/collector.*\) v1\.60.0/\1 v1.61.0/" go.mod sed -i '' "s/\(github.com\/open-telemetry\/opentelemetry-collector-contrib\/.*\) v0\.154.0/\1 v0.155.0/" go.mod * go mod tidy && make notice * chore: update distro version (cherry picked from commit 539bc0e) # Conflicts: # NOTICE.txt # go.mod # go.sum # x-pack/otel/distributions/beats-otel-collector/manifest.yaml * fix: resolve go.mod conflicts, run go mod tidy && make notice * chore: resolve OTel manifest export version conflicts * chore: remove unavailable logstash exporter from 8.19 manifest --------- Co-authored-by: Andrzej Stencel <andrzej.stencel@elastic.co> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Proposed commit message
Updates the OpenTelemetry Collector dependencies to the current latest versions
v0.155.0andv1.61.0. See changes sincev0.154.0/v1.60.0for 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 inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally