Skip to content

v0.3.0 - Scheduled Scan Cron Health

Choose a tag to compare

View all tags
@NichlasB NichlasB released this 21 Jun 21:12
· 21 commits to master since this release
v0.3.0
dad1a78

What's New in v0.3.0

This release adds scheduled-scan cron health tracking so administrators can see whether scans are being triggered by WP-CLI/server cron, HTTP WP-Cron, or another runtime path. It also carries forward the scan-state UI improvements that make UTC timing, next scan timing, and recent events easier to compare.

Highlights

  • Adds cron-health evidence for scheduled scans, including WP-CLI and HTTP WP-Cron tracking.
  • Adds a Server Cron Expected setting with admin warnings when WP-CLI scan evidence is missing.
  • Improves scan observability with current UTC time, next scheduled scan state, and clearer recent-event timing.

Changelog

Added

  • Added cron health tracking for scheduled scans, including last runner evidence, WP-CLI scan evidence, WP-Cron disabled status, and server-cron health guidance.
  • Added a Server Cron Expected setting that warns administrators when automatic scans should be driven by WP-CLI but no WP-CLI scheduled scan has been observed.
  • Added a dedicated Scan State section showing current UTC time, automatic scan status, next scheduled scan timing, last completed scan, and minimum file age in seconds.

Changed

  • Display Recent Events timestamps in explicit UTC format and add a current UTC time reference above the events table.

Upgrade Notes

No breaking changes in this release.

Assets 3
Loading