Ian Littman 89ca35c66b Switch vulns cron false positive clear to clear vulns based on when the vulns run started, rather than based on periodicity (#31364) ... Fixes #26404. This means that for long vulns runs vulns will stick around longer, so we don't wind up nuking vulns that were added earlier in the run, and in cases where the vulns run takes less than 2h we'll see vulns clear cleanly more quickly. # Checklist for submitter If some of the following don't apply, delete the relevant line. - [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/guides/committing-changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) ## Testing - [x] Added/updated automated tests - [ ] QA'd all new/changed functionality manually --------- Co-authored-by: Jahziel Villasana-Espinoza <jahziel@fleetdm.com>		2025-07-29 10:14:14 -05:00
..
matching_rules.go	Switch vulns cron false positive clear to clear vulns based on when the vulns run started, rather than based on periodicity (#31364)	2025-07-29 10:14:14 -05:00
matching_rules_test.go	Switch vulns cron false positive clear to clear vulns based on when the vulns run started, rather than based on periodicity (#31364)	2025-07-29 10:14:14 -05:00