Skip to content

Yeraze/meshmonitor

v4.1.1 Breaking

This release includes breaking changes for platform teams planning a safe upgrade.

Published 1mo Monitoring & Metrics
✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

meshcore meshtastic mqtt

Summary

AI summary

Fixed several regressions including MQTT/IP hop labeling, virtual‑node channel name loss, custom map‑pin overwrites, packet‑log retention failures, and notification fallback ignoring saved notify* values.

Full changelog

MeshMonitor v4.1.1

Hotfix release for v4.1.0 addressing several user-reported regressions: an MQTT/IP hop labelling bug in traceroute, a virtual-node MQTT uplink that lost its primary-channel name, custom map-pin locations being overwritten by node telemetry, packet-log retention failing on PostgreSQL/MySQL, channel-database UI rejecting empty channel names, and notification-preference legacy-fallback ignoring saved notify* values. Map Analysis gains link/trail detail in the inspector and consistent pin styling. The tooling side adds exit-code-driven CI/release watcher scripts plus a /release-monitor skill, and the security docs now document the kernel CVE policy and Helm seccomp default.

Bug Fixes

  • Notifications: legacy preference fallback now honors saved notify* values — #2868 (closes #2867)
  • Virtual node: synthesize a primary channel name from the modem preset for MQTT uplink — #2866
  • Traceroute: stop labelling RF hops as MQTT/IP — #2862 (closes #2859)
  • Map: preserve manual position override across WebSocket node updates — #2858 (closes #2847)
  • Database: portable two-step delete for packet log retention — #2857 (closes #2846)
  • Channels: allow empty channel names; render slot 0 as "Primary" when blank — #2856 (closes #2855)

Features

  • Map Analysis: shared pin style for node markers — #2865
  • Map Analysis: show neighbor link and trail details in inspector — #2863

Documentation

  • Security: kernel CVE policy + Helm seccomp default — #2860

CI / Tooling

  • Exit-code-driven watch-ci.sh + watch-release.sh + /release-monitor skill — #2870
  • Bump to 4.1.1 + News.json blurb — #2869

Issues Resolved

  • #2867 — Toggle audio notification for successful traceroute
  • #2859 — 4.1.0 using MQTT even when disabled
  • #2855 — Empty channel names rejected by Channel Database UI
  • #2847 — Custom Location overwritten by node telemetry (fixedPosition)
  • #2846 — Packet log retention delete portable across backends

Upgrade Notes

No breaking changes or migrations. Standard upgrade.

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v4.1.0...v4.1.1

🚀 MeshMonitor v4.1.1

📦 Installation

Docker (recommended):

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

🧪 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.

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.

Sign up free

About Yeraze/meshmonitor

All releases →

Related context

Earlier breaking changes

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

Beta — feedback welcome: [email protected]