Ian Littman bbc35cb76b Include pre-releases when building osquery version list constant (#25089) ... Also updates said constant via this script to include 5.15.0. Idea for this is that including pre-releases as they're published ensures that by the time the corresponding Fleet release ships we have a current list, without having to cherry-pick these updates. # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Manual QA for all new/changed functionality		2025-01-02 11:38:15 -06:00
..
actions/r2-upload	Keep all fleetd-base and fleetd-chrome artifacts. (#19749)	2024-06-17 15:49:06 -05:00
ISSUE_TEMPLATE	Update user story issue template (#25006)	2024-12-24 13:41:33 -05:00
scripts	Include pre-releases when building osquery version list constant (#25089)	2025-01-02 11:38:15 -06:00
workflows	Release osqueryd 5.15.0 (#25087)	2025-01-02 11:41:03 -03:00
dependabot.yml	Remove daily schedule so it only gets triggered by security alerts (#14871)	2023-11-02 09:53:40 -05:00
pull_request_template.md	Add checkbox to change frontend/CLI if API paths are modified (#21316)	2024-08-14 14:28:48 -04:00