Skip to content

Yeraze/meshmonitor

v3.9.1 Feature

This release adds 1 notable feature for engineering teams evaluating rollout.

Published 2mo 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

Affected surfaces

breaking_upgrade

Summary

AI summary

Fixed migration failure when auto_key_repair_log table is missing across SQLite, PostgreSQL, and MySQL.

Full changelog

v3.9.1 - Hotfix

Bug Fixes

  • fix: migration 084 fails when auto_key_repair_log table doesn't exist (#2249, closes #2247) — Users upgrading to 3.9.0 who never enabled auto-key management would hit SQLite errors on the Security page. Migration now checks table existence before altering on all three backends (SQLite, PostgreSQL, MySQL), and query methods gracefully handle missing table/columns.

Features

  • feat: configurable zoom level for neighbor info lines (#2246, closes #2245) — Added a setting in the Map section to control the zoom level at which Neighbor Info lines are hidden. Defaults to 12 (previous hardcoded value).

Documentation

  • docs: update architecture lessons and CLAUDE.md (#2248) — Added Key Management & PKI section, settings allowlist guidance, and version bump file list.

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

🚀 MeshMonitor v3.9.1

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:3.9.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]