build(deps): bump github.com/microsoft/wmi from 0.38.3 to 0.42.0 in the windows group across 1 directory

[dependabot]

Bumps the windows group with 1 update in the / directory: github.com/microsoft/wmi.

Updates github.com/microsoft/wmi from 0.38.3 to 0.42.0

Commits

• 2b4d93b Merge pull request #190 from microsoft/madhanm/go-1.26
• e294b52 chore: update Go to 1.26.0
• 71c4d5c Merge pull request #189 from microsoft/fix/instancemanager-nil-session-guard
• a13d3b8 fix: prevent WMI panics from nil cache poisoning, nil properties, and unsafe ...
• c33bbdd Merge pull request #188 from microsoft/copilot/ensure-green-status-checks
• f0e2be0 Add GitHub Copilot instructions for PR status checks
• eea25b8 Initial plan
• ff19dce Merge pull request #187 from microsoft/copilot/update-go-version-1-25
• 2bfb1a0 Revert go.sum removal - retain go.sum in repository
• 46037b7 Optimize Makefile to avoid redundant vendor runs
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[github-actions]

🤖 GitHub comments

Just comment with:

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

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @dependabot[bot]? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[coderabbitai]

Caution

Review failed

An error occurred during the review process. Please try again later.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch dependabot/go_modules/main/windows-d86c4de300

• 🛠️ Update Documentation

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@go.mod`:
- Line 3: The repo's go.mod now requires "go 1.26" which mismatches the CI's Go
1.25.8 runtime; update the CI configuration to install/use Go 1.26 (or set
GOTOOLCHAIN=go1.26) so the pipeline runtime matches the go.mod requirement,
e.g., change the CI workflow/runner setup to use Go 1.26 or export
GOTOOLCHAIN=go1.26 before build steps to ensure the "go 1.26" constraint in
go.mod is satisfied.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 33c0bfdd-c8f2-478f-a65f-506e2e4797c8

📥 Commits

Reviewing files that changed from the base of the PR and between 1b1113d and 5049135.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300

[github-actions]

TL;DR

The golangci-lint workflow run failed because the lint (macos-latest) job hit the linter timeout (--timeout=30m) and exited with code 4. Immediate action: re-run the failed job; if it repeats, raise the macOS lint timeout or reduce lint workload for that leg.

Remediation

• Re-run lint (macos-latest) for workflow run 26470349790 to confirm whether this was a transient runner/performance timeout.
• If it fails again the same way, increase the timeout used by the lint action for this workflow (currently golangci-lint run ... --timeout=30m) and/or reduce work on that job so it completes within the time budget.

Investigation details

Root Cause

The failing job does not report lint violations; it reports a timeout from golangci-lint after ~38 minutes, then exits non-zero. The run has one failed job (lint (macos-latest)), with the golangci-lint step marked as failed.

Evidence

• Workflow: https://github.com/elastic/beats/actions/runs/26470349790
• Job/step: lint (macos-latest) → golangci-lint (job: https://github.com/elastic/beats/actions/runs/26470349790/job/77941801107)
• Key log excerpt:
  • Running [.../golangci-lint run ... --timeout=30m --whole-files]
  • level=error msg="Timeout exceeded: try increasing it by passing --timeout option"
  • ##[error]golangci-lint exit with code 4

Validation

• Not run (read-only investigation of CI logs only).

Follow-up

• Check whether recent dependency/merge changes for this PR increased analyzer runtime on macOS specifically, since the Windows and Ubuntu lint jobs in the same run completed successfully.

---

What is this? | From workflow: PR Actions Detective

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

[github-actions]

TL;DR

Buildkite https://buildkite.com/elastic/beats/builds/46808 failed in :ubuntu: Filebeat: Go Integration Tests before tests ran because Docker packaging cannot pull the Wolfi base image (cgr.dev/chainguard/wolfi-base:latest returns not found). Immediate action: update Beats Docker packaging base image reference to a valid/pinned Wolfi image (or temporarily disable Wolfi package targets for this lane).

Remediation

• Replace untagged Wolfi references in packaging config with a known-good explicit tag or digest (currently they resolve as :latest):
  • dev-tools/packaging/packages.yml:174 (buildFrom: '--platform=linux/amd64 cgr.dev/chainguard/wolfi-base')
  • dev-tools/packaging/packages.yml:202 (from: '--platform=linux/amd64 cgr.dev/chainguard/wolfi-base')
  • (and arm64 variants at dev-tools/packaging/packages.yml:187,207).
• Re-run the failing Buildkite lane after updating image reference(s).

Investigation details

Root Cause

The Dockerfile used by packaging sets FROM \{\{ .buildFrom }} (dev-tools/packaging/templates/docker/Dockerfile.tmpl:7) and FROM \{\{ .from }} (dev-tools/packaging/templates/docker/Dockerfile.tmpl:38). For Wolfi variants, packages.yml provides cgr.dev/chainguard/wolfi-base without an explicit tag/digest, so Docker resolves :latest.

In this run, registry resolution for that image fails with not found, so package image build exits non-zero and mage goIntegTest job fails at packaging stage.

Evidence

• Build: https://buildkite.com/elastic/beats/builds/46808
• Job/step: :ubuntu: Filebeat: Go Integration Tests (pipeline filebeat, build https://buildkite.com/elastic/filebeat/builds/32972)
• Key log excerpt:
  • ERROR: failed to solve: cgr.dev/chainguard/wolfi-base: failed to resolve source metadata for cgr.dev/chainguard/wolfi-base:latest: ... not found
  • Error: failed building filebeat-oss-wolfi ... failed to build docker

Verification

• Not run locally (detective workflow is read-only); conclusion is based on Buildkite logs and repository packaging templates/config.

Follow-up

• If a valid Wolfi tag is already standardized elsewhere in the repo/org, reuse that same tag/digest here to avoid future latest drift/breakage.

---

What is this? | From workflow: PR Buildkite Detective

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

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b dependabot/go_modules/main/windows-d86c4de300 upstream/dependabot/go_modules/main/windows-d86c4de300
git merge upstream/main
git push upstream dependabot/go_modules/main/windows-d86c4de300