Skip to content

Conversation

@mergify
Copy link
Contributor

@mergify mergify bot commented Nov 5, 2025

Proposed commit message

See title

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. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

## Disruptive User Impact
## Author's Checklist
## How to test this PR locally
## Related issues
## Use cases
## Screenshots
## Logs


This is an automatic backport of pull request #47461 done by [Mergify](https://mergify.com).

(cherry picked from commit 4ded660)

# Conflicts:
#	NOTICE.txt
#	go.mod
#	go.sum
@mergify mergify bot added the backport label Nov 5, 2025
@mergify mergify bot requested a review from a team as a code owner November 5, 2025 14:50
@mergify mergify bot added conflicts There is a conflict in the backported pull request backport labels Nov 5, 2025
@mergify mergify bot added the conflicts There is a conflict in the backported pull request label Nov 5, 2025
@mergify
Copy link
Contributor Author

mergify bot commented Nov 5, 2025

Cherry-pick of 4ded660 has failed:

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

You are currently cherry-picking commit 4ded660aa.
  (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)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum

no changes added to commit (use "git add" and/or "git commit -a")

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 Nov 5, 2025
@github-actions github-actions bot added Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team skip-changelog labels Nov 5, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Nov 5, 2025

🤖 GitHub comments

Just comment with:

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

@elasticmachine
Copy link
Collaborator

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 Nov 5, 2025
@belimawr
Copy link
Contributor

belimawr commented Nov 5, 2025

Closing in favour of #47486 that updates elastic-agent-libs and the code using it.

@belimawr belimawr closed this Nov 5, 2025
@mergify mergify bot deleted the mergify/bp/9.2/pr-47461 branch November 5, 2025 18:20
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 skip-changelog 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