Change codeowners for prior SecML packages to TRaDE team - #20662
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Resolved conflicts in package manifests and changelogs by bumping patch versions and updating owner to threat-research-and-detection-engineering. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
This comment has been minimized.
This comment has been minimized.
This comment was marked as outdated.
This comment was marked as outdated.
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
|
Queued — the merge queue status continues in this comment ↓. |
Merge Queue Status
Required conditions to enter a queue
|
☑️ The pull request has been merged manuallyDetailsThe pull request has been merged manually at c4d3f0e |
|
Package beaconing - 1.7.1 containing this change is available at https://epr.elastic.co/package/beaconing/1.7.1/ |
|
Package ded - 3.4.1 containing this change is available at https://epr.elastic.co/package/ded/3.4.1/ |
|
Package dga - 3.2.1 containing this change is available at https://epr.elastic.co/package/dga/3.2.1/ |
|
Package hta - 2.0.1 containing this change is available at https://epr.elastic.co/package/hta/2.0.1/ |
|
Package lmd - 3.4.1 containing this change is available at https://epr.elastic.co/package/lmd/3.4.1/ |
|
Package pad - 2.4.1 containing this change is available at https://epr.elastic.co/package/pad/2.4.1/ |
|
Package problemchild - 3.2.1 containing this change is available at https://epr.elastic.co/package/problemchild/3.2.1/ |
Proposed commit message
Reassigns Security ML packages to the Threat Research and Detection Engineering team as ownership has changed.
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.changelog.ymlfile.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 practicesAuthor's Checklist
How to test this PR locally
Related issues
Screenshots