osquery_manager 1.26.0: osquery 5.22.1, Kibana ^9.4.0, osquery-gen beats tag/branch#18305
Merged
marc-gr merged 2 commits intoelastic:mainfrom Apr 9, 2026
Merged
osquery_manager 1.26.0: osquery 5.22.1, Kibana ^9.4.0, osquery-gen beats tag/branch#18305marc-gr merged 2 commits intoelastic:mainfrom
marc-gr merged 2 commits intoelastic:mainfrom
Conversation
…ats tag/branch - Regenerate schemas and fields for osquery 5.22.1; bump package and Kibana constraint. - Add optional beats.tag and beats.branch in osquery-gen (tag > branch > version).
marc-gr
force-pushed
the
feat/upgrade-osquery
branch
from
19e63bc to
f522455
Compare
Contributor
Vale Linting ResultsSummary: 1 warning found
|
| File | Line | Rule | Message |
|---|---|---|---|
| packages/osquery_manager/_dev/scripts/osquery-gen/README.md | 7 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'for example' instead of 'e.g'. |
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.
marc-gr
added
enhancement
|
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
marc-gr
added
the
Team:Defend Workflows
💚 Build Succeeded
|
andrewkroh
added
the
documentation
brian-mckinney
approved these changes
Apr 9, 2026
|
Package osquery_manager - 1.26.0 containing this change is available at https://epr.elastic.co/package/osquery_manager/1.26.0/ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
osquery_manager 1.26.0: upgrade osquery schema to 5.22.1, Kibana ^9.4.0, osquery-gen beats ref options
1.26.0, regeneratedosquery.yml/osquery.jsonandmetadata.jsonfrom osquery-gen for osquery 5.22.1, and raised the Kibana condition to ^9.4.0. Extended osquery-genconfig.ymlso beats can be pinned with optionaltagorbranch(precedence: tag > branch > semverversion), with the same GitHub API probe used before to ensure extension specs exist at that ref. Documented behavior in the generator README and config comments.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
From the repo root (or the generator directory):
With
elastic-packageonPATH, omit-skip-package-checkto run the package check. Confirmpackages/osquery_manager/schemas/metadata.jsonreflects the expectedosquery_versionand that optionalbeats.tag/beats.branchinconfig.ymlresolve when set.Related issues
Screenshots