Yeraze/meshmonitor v2.12.4

v2.12.4: Fix Security Scanner last scan timestamp

on GitHub

Bug Fixes

Security Scanner

• Fixed Security Scanner "Last Scan" timestamp not updating - The "Last Scan" field on the Security page now properly displays when manual scans are run, instead of always showing "Never". #419 fixes #418

Technical Details

The previous implementation incorrectly used node lastHeard timestamps (when mesh messages were received) as a proxy for scan completion time. This has been replaced with proper scan timestamp tracking in the DuplicateKeySchedulerService.

Changes:

• Added lastScanTime property to track scan completion
• Updated runScan() to set timestamp when scans complete
• Updated getStatus() API to return accurate scan timestamps
• Removed broken workaround from security routes

Full Changelog

Merged Pull Requests:

• fix: Update Security Scanner last scan timestamp #419

Closed Issues:

• Security Scanner: Last Scan is not updated #418

Full Diff: v2.12.3...v2.12.4

🚀 MeshMonitor v2.12.4

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:v2.12.4

🧪 Testing

✅ All tests passed
✅ TypeScript checks passed
✅ Docker images built for linux/amd64, linux/arm64, linux/arm/v7

📋 Changes

See commit history for detailed changes.