Skip to content

[9.2](backport #48816) Update elastic-agent-system-metrics to v0.14.0#48859

Merged
ycombinator merged 5 commits into9.2from
mergify/bp/9.2/pr-48816
Feb 24, 2026
Merged

[9.2](backport #48816) Update elastic-agent-system-metrics to v0.14.0#48859
ycombinator merged 5 commits into9.2from
mergify/bp/9.2/pr-48816

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Feb 13, 2026

Summary

  • Bump github.com/elastic/elastic-agent-system-metrics from v0.13.6 to v0.14.0
  • Regenerate NOTICE.txt to reflect the updated dependency version
  • Add changelog fragment

🤖 Generated with Claude Code


This is an automatic backport of pull request #48816 done by Mergify.

@mergify mergify bot added the backport label Feb 13, 2026
@mergify mergify bot requested a review from a team as a code owner February 13, 2026 21:17
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Feb 13, 2026
@mergify mergify bot requested a review from a team as a code owner February 13, 2026 21:17
@mergify mergify bot requested review from belimawr and mauri870 and removed request for a team February 13, 2026 21:17
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Feb 13, 2026

Cherry-pick of 22bedbc has failed:

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

You are currently cherry-picking commit 22bedbc8b.
  (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:
	new file:   changelog/fragments/1770852460-bump-elastic-agent-system-metrics-to-v0.14.0.yaml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	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 Feb 13, 2026
@github-actions
Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

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

@github-actions github-actions bot added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Feb 13, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

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 Feb 13, 2026
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Feb 16, 2026

This pull request has not been merged yet. Could you please review and merge it @ycombinator? 🙏

@ycombinator ycombinator enabled auto-merge (squash) February 18, 2026 22:13
@ycombinator ycombinator force-pushed the mergify/bp/9.2/pr-48816 branch 2 times, most recently from 1643585 to ad14e22 Compare February 20, 2026 12:59
@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Feb 20, 2026

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 mergify/bp/9.2/pr-48816 upstream/mergify/bp/9.2/pr-48816
git merge upstream/9.2
git push upstream mergify/bp/9.2/pr-48816

@mergify
Copy link
Copy Markdown
Contributor Author

mergify bot commented Feb 23, 2026

This pull request has not been merged yet. Could you please review and merge it @ycombinator? 🙏

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
(cherry picked from commit 22bedbc)

# Conflicts:
#	NOTICE.txt
#	go.mod
#	go.sum
@ycombinator ycombinator force-pushed the mergify/bp/9.2/pr-48816 branch 2 times, most recently from c369326 to c3f394c Compare February 23, 2026 18:11
@ycombinator ycombinator force-pushed the mergify/bp/9.2/pr-48816 branch from c3f394c to 97e5273 Compare February 23, 2026 18:12
@github-actions
Copy link
Copy Markdown
Contributor

CI failure is in workflow run 22318710042, job check, step Run check-default: go install github.com/magefile/mage exits with go: 'go install' requires a version when current directory is not in a module.

Root cause: the step is executing in a directory where go.mod is not detected (or Go is treating it as outside a module), and since Go now requires an explicit version in that case, the install command fails before make check-default runs.

Recommended minimal fix:

  • In .github/workflows/check-default.yml, change go install github.com/magefile/mage to go install github.com/magefile/mage@latest (or pin a specific version, e.g. @v1.15.0) so it is independent of working directory/module context.
  • Optionally add working-directory: $\{\{ github.workspace }} to the step for extra safety.

Validation I ran locally:

  • cd /home/runner/work/beats && go install github.com/magefile/mage reproduces the same error.
  • The failure occurs before repository checks/tests execute, so no PR code path was exercised in this failed run.

What is this? | From workflow: PR CI Detective

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

@github-actions
Copy link
Copy Markdown
Contributor

CI failure is isolated to lint (windows-latest) in workflow run 22318698373 (job 64570746967). golangci-lint fails with typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies, and the same log shows set GOMOD=NUL plus unable to read module file go.mod, meaning the checked-out commit for that run (c369326e714357135076ffaf98a5a581701d91fb) did not contain root module files (go.mod/go.sum) at lint time.

Recommended fix:

  • Ensure the backport branch contains root go.mod and go.sum (conflict resolution likely dropped them in commit c369326e...).
  • Push the fix (or rerun on a commit that already restores those files), then re-run golangci-lint.

Evidence from logs:

  • level=warning ... unable to read module file go.mod
  • level=error ... pattern ./...: directory prefix . does not contain main module
  • ##[error]golangci-lint exit with code 7

Tests run by me:

  • Workflow/job log inspection only (no local test execution).

What is this? | From workflow: PR CI Detective

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

@github-actions
Copy link
Copy Markdown
Contributor

CI failure is in golangci-lint on macos-latest only (job 64571238845); Ubuntu and Windows passed.

Root cause from logs:

  • golangci-lint run --timeout=30m --whole-files started at 18:12:34Z and ended at 18:49:05Z (~36m)
  • It reported 0 issues and then failed with Timeout exceeded: try increasing it by passing --timeout option (exit code 4)

Recommended remediation (minimal):

  • Increase the timeout in .github/workflows/golangci-lint.yml (args: --timeout=30m --whole-files) to at least 45m (or 60m for headroom), then rerun this check.
  • This appears to be infra/perf timing on macOS rather than a code-quality regression in this PR.

Tests run by me:

  • No local tests executed; analysis based on workflow run 22318836283 job logs and job metadata.

What is this? | From workflow: PR CI Detective

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

@rdner
Copy link
Copy Markdown
Member

rdner commented Feb 24, 2026

Blocked by #49056

@rdner
Copy link
Copy Markdown
Member

rdner commented Feb 24, 2026

Now blocked by #48485

@ycombinator ycombinator merged commit 87f1b85 into 9.2 Feb 24, 2026
206 checks passed
@ycombinator ycombinator deleted the mergify/bp/9.2/pr-48816 branch February 24, 2026 15:31
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 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.

3 participants