chore(deps): bump golang.org/x/tools from 0.47.0 to 0.48.0

[dependabot]

Bumps golang.org/x/tools from 0.47.0 to 0.48.0.

Commits

• 05f9cb5 go.mod: update golang.org/x dependencies
• 745d7ae gopls: add CompiledAsmFiles in cache.Package
• 797ee67 go/ssa: make Const(unsafe.Pointer, nil).IsNil() true
• 9751125 gopls/internal/test: Completion benchmarks use empty range
• 8786a96 internal/stdlib: update stdlib index for Go 1.27 Release Candidate 2
• 425085f gopls/internal/server: modify return of parseAction
• 30c4f87 go/analysis/passes/nilness: skip magic cgo functions
• 9e6441d gopls/internal/protocol/generate: remove manual rename overwritten
• df96841 gopls/internal/protocol: use Debug log level
• 278f062 gopls/internal/protocol: update to LSP 3.18
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[infra-vault-gh-plugin-prod]

💔 Build Failed

• Buildkite Build
• Commit: 0ba0e44

Failed CI Steps

• Check integrations prisma_access

History

[github-actions]

TL;DR

The Check integrations prisma_access Buildkite step failed during CI environment setup, not during the prisma_access package tests. apt-get update hit an Ubuntu mirror sync inconsistency (File has unexpected size ... Mirror sync in progress?), so this is an infrastructure/transient dependency-index failure; retry the failed Buildkite job.

Remediation

• Retry the failed Check integrations prisma_access job in Buildkite.
• If the same APT mirror error repeats, handle it in CI setup by wrapping the Docker setup apt-get update with the existing retry helper in .buildkite/scripts/common.sh, rather than changing this Dependabot PR.

Investigation details

Root Cause

Classification: Infrastructure.

The failure occurs before package processing starts. .buildkite/scripts/test_one_package.sh:21-24 runs shared setup helpers, including with_docker, before process_package is called at .buildkite/scripts/test_one_package.sh:30. In .buildkite/scripts/common.sh:130-155, with_docker runs sudo apt-get update before installing the pinned Docker packages. That setup command failed because the Ubuntu security mirror returned package index metadata with a mismatched file size/hash while syncing.

The PR only changes go.mod and go.sum for golang.org/x/tools and related golang.org/x/* modules, so there is no evidence that the dependency bump caused this setup failure.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/45802
• Job/step: Check integrations prisma_access
• Key log excerpt:

E: Failed to fetch (security.ubuntu.com/redacted)  File has unexpected size (1041412 != 1041636). Mirror sync in progress? [IP: 91.189.91.83 80]
...
E: Some index files failed to download. They have been ignored, or old ones used instead.
🚨 Error: The command exited with status 100

Verification

• Not run locally: the failure is in remote Buildkite host setup against the Ubuntu APT mirror, before repository tests execute. A local package test would not validate the transient mirror state that failed this job.

Follow-up

• No PR code change is indicated unless a retry reproduces a package-specific failure after setup completes.

---

What is this? | From workflow: PR Buildkite Detective

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

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

Package crowdstrike 👍(10) 💚(2) 💔(2)

Expand to view

Data stream	Previous EPS	New EPS	Diff (%)	Result
falcon	5847.95	2973.54	-2874.41 (-49.15%)	💔
identity_protection_timeline	9756.1	8110.3	-1645.8 (-16.87%)	💔

To see the full report comment with /test benchmark fullreport

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request