Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.18](backport #43426) [osquerybeat] Upgrade to 5.15.0 #43614

Open
wants to merge 1 commit into
base: 8.18
Choose a base branch
from
Open

[8.18](backport #43426) [osquerybeat] Upgrade to 5.15.0 #43614

wants to merge 1 commit into from
+6 −5

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 31, 2025

Proposed commit message

Upgrade the upstream osquery version included with osquerybeat to 5.15.0.

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
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

This will change osquery tables caused by the changes included in upstream osquery

Related PRs

@mjwolf @mergify
[osquerybeat] Upgrade to 5.15.0 (#43426)
d4a386a 
Upgrade the upstream osquery version included with osquerybeat to 5.15.0.

(cherry picked from commit 7124d51)
@mergify mergify bot added the backport label Mar 31, 2025
@mergify mergify bot requested a review from a team as a code owner March 31, 2025 17:30
@mergify mergify bot assigned mjwolf Mar 31, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Mar 31, 2025
@github-actions github-actions bot added breaking change Osquerybeat Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution labels Mar 31, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/sec-deployment-and-devices (Team:Security-Deployment and Devices)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@mjwolf mjwolf

Labels
backport breaking change Osquerybeat Team:Security-Deployment and Devices Deployment and Devices Team in Security Solution
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @mjwolf