Yeraze/meshmonitor

v3.9.2 Bugfix

This release fixes issues for SREs watching stability and regressions.

Published 2mo Monitoring & Metrics

✓ No known CVEs patched

✓ No known CVEs patched in this version

Topics

meshcore meshtastic mqtt

Summary

AI summary

Fixed incorrect property names in Postgres/MySQL pool handling causing errors on the Security page.

Full changelog

fix: wrong property names for Postgres/MySQL pools in getKeyRepairLogAsync (#2251) — The key mismatch history query used incorrect property names (pgPool instead of postgresPool) causing Cannot read properties of undefined (reading 'connect') errors on PostgreSQL and MySQL backends when viewing the Security page.

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.9.1...v3.9.2

Docker (recommended):

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

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

See commit history for detailed changes.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track Yeraze/meshmonitor

Get notified when new releases ship.

About Yeraze/meshmonitor

v4.7.2 Route `destination` field now rejects non‑8‑hex nodeId or 64‑hex publicKey, returning HTTP 400.