Update elastic-package to v0.126.1

[teresaromero]

Proposed commit message

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

TL;DR

The Buildkite failure is caused by a repository hygiene check detecting an out-of-date go.sum after dependency checks. Regenerate and commit go.sum for this branch, then rerun CI.

Remediation

• Run go mod tidy (or the repository’s standard dependency sync command used for dev/ Go modules) and commit the resulting go.sum update.
• Re-run Check go sources to confirm no tracked files change after the check script.

Investigation details

Root Cause

The failing step is not a unit test failure (all Go tests passed), but a post-check “working tree must stay clean” guard in .buildkite/scripts/check_sources.sh execution. The job reports a modified dependency file after checks:

• go.sum: needs update

That indicates the PR’s dependency metadata is inconsistent with current module requirements at commit f59c350ff432e667c0f930b3c47195124e5ae2a2.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/48967
• Job/step: :white_check_mark: Check go sources
• Key log excerpt (from /tmp/gh-aw/buildkite-logs/integrations-white_check_mark-check-go-sources.txt):
  • DONE 443 tests in 1.533s
  • --- Check if any files modified
  • go.sum: needs update
  • Error: The command exited with status 1

Verification

• Not run locally in this environment; conclusion is based on Buildkite log evidence and PR metadata.

Follow-up

If go mod tidy does not produce changes locally, run the exact repo check script (.buildkite/scripts/check_sources.sh) in the same module context to identify which dependency check mutates go.sum.

---

What is this? | From workflow: PR Buildkite Detective

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

[Copilot]

🟢 Approval recommended

The changes are a straightforward dependency/version bump with consistent go.mod/go.sum updates and no evident issues in the updated module graph.

Pull request overview

This PR updates the Go module dependencies used by github.com/elastic/integrations, primarily bumping github.com/elastic/elastic-package to v0.126.1 to pick up the referenced google-sdk artifact rename fix needed for CI reliability.

Changes:

• Bump github.com/elastic/elastic-package from v0.125.0 to v0.126.1.
• Refresh related Go dependencies (e.g., testify, golang.org/x/*, OpenTelemetry modules) and their checksums as part of the module update.

File summaries

File	Description
go.mod	Updates the required elastic-package version and aligns dependent module versions accordingly.
go.sum	Updates/records checksums for the new dependency graph resulting from the version bump.

Review details

• Files reviewed: 1/2 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: 3572ae0

Failed CI Steps

• Check integrations aws

History

• 💔 Build #48967 failed f59c350

[teresaromero]

closing as the change has been included here #20973