Skip to content

Yeraze/meshmonitor

v4.6.6 Breaking

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

Published 11d 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

ReleasePort's take

Light signal
editorial:auto 11d

The Router role now persists when selected in the Remote Admin UI dropdown, and the Auto‑upgrade halted banner clears after a successful auto‑update. Additionally, Proxmox LXC deployments gain an automated update script (lxc/update-lxc.sh).

Why it matters: Fixes prevent unintended role reversion and stale upgrade alerts; the new update script streamlines Proxmox LXC maintenance.

Summary

AI summary

Updates Bug Fixes, Issues Resolved, and πŸš€ MeshMonitor v4.6.6 across a mixed release.

Changes in this release

Feature Medium

Adds automated update script for Proxmox LXC (`lxc/update-lxc.sh`).

Adds automated update script for Proxmox LXC (`lxc/update-lxc.sh`).

Source: llm_adapter@2026-05-24

Confidence: high

β€”
Bugfix Medium

Router role no longer reverts when selected in Remote Admin β†’ Device Configuration.

Router role no longer reverts when selected in Remote Admin β†’ Device Configuration.

Source: llm_adapter@2026-05-24

Confidence: high

β€”
Bugfix Medium

Auto‑upgrade halted banner clears after a successful auto‑update.

Auto‑upgrade halted banner clears after a successful auto‑update.

Source: llm_adapter@2026-05-24

Confidence: low

β€”
Bugfix Medium

UDP/RF filters now correctly hide neighbor-info lines when unchecked.

UDP/RF filters now correctly hide neighbor-info lines when unchecked.

Source: granite4.1:30b@2026-05-24-audit

Confidence: low

β€”
Full changelog

MeshMonitor v4.6.6

Patch release with two user-reported bug fixes, a new automated update path for Proxmox LXC, and documentation polish. The headline fixes: picking Router in the Remote Admin role dropdown no longer silently reverts, and the red auto-upgrade halted banner no longer lingers after a successful auto-update completes. LXC operators get a new in-place update script so they no longer have to redeploy from template for every release. Blog posts now have proper breadcrumbs + title + date + tag headers, and the blog index goes full-width for a real 3-column layout.

Bug Fixes

  • #3148 β€” Show UDP / Show RF filters now correctly hide neighbor-info lines (closes #3147)
  • #3153 β€” Router role no longer reverts when selected in Remote Admin β†’ Device Configuration. The native window.confirm() that gated the selection was easy to dismiss accidentally, leaving the dropdown snapped back. Replaced with a persistent inline warning banner under the role display.
  • #3155 β€” Auto-upgrade banner ("halted after repeated failures") no longer persists after a successful auto-update. The persisted autoUpgradeBlocked flag is now self-healed when the most recent upgrade is 'complete', so the banner clears on the next status poll even if markCompleteAndClear() was skipped during the upgrade flow (e.g. no frontend session was open to call /api/upgrade/status in the post-restart window).

Features

  • #3146 β€” Automated update script for Proxmox LXC (lxc/update-lxc.sh). Operators can now update existing LXC containers in-place instead of redeploying from a fresh template each release.

Documentation

  • #3150 β€” New "Hurricane Preparedness" guide and a new guide blog category for longer-form operator write-ups
  • #3152 β€” Blog UX polish: full-width 3-tile index layout, plus a real post header on individual entries (breadcrumbs, title, formatted publish date, category / priority / tags badges). Adds optional tags: frontmatter field.

Issues Resolved

  • #3144 β€” [FEAT] Automate Update of LXC Script
  • #3147 β€” [BUG] UDP bridge nodes still appear on map when "Show UDP" is unchecked (fix landed in #3148)

Upgrade Notes

No breaking changes; no migrations. Drop-in upgrade from v4.6.5.

If your instance still shows the red auto-upgrade halted banner after upgrading to 4.6.6, it will clear on the next page load (the self-heal runs whenever /api/upgrade/status is polled and the most recent upgrade in history is complete).

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v4.6.5...v4.6.6

πŸš€ MeshMonitor v4.6.6

πŸ“¦ Installation

Docker (recommended):

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

πŸ§ͺ 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]