MeshMonitor v4.0.0-beta7

⚠️ Pre-release — testing/feedback build. Not recommended for production. No :latest Docker tag will be published.

Summary

Bug-fix focused beta that hardens per-source scoping and virtual-node workflows introduced in 4.0. The Info page now correctly reflects the active source for both display and the Connection Status card's Node Address. Auto Announce's Send Now and scheduler restarts are scoped to the correct source, and Virtual Node bootstrap/scoping was corrected. The auto-responder now honors a script's private field to force DM vs. channel override. Node upserts preserve favoriteLocked and positionOverride so telemetry no longer overwrites them after restart. Traceroute rows are excluded from the UI message window (fixes last-message disappearing on successful traceroute). A legacy FK-to-nodes(nodeNum) migration path for 3.12 → 4.0 upgrades was added. Dependency bumps and a CI isolation fix for the api-exercise test round out the release.

Bug Fixes

• #2747 — auto-responder: honor script private field for DM/channel override
• #2746 — nodes: preserve favoriteLocked + positionOverride across upserts (#2743)
• #2745 — messages: exclude traceroute rows from UI message window (#2741)
• #2744 — per-source: scope Info page Node Address to active source (#2731)
• #2740 — migrations: handle legacy FK to nodes(nodeNum) on 3.12 → 4.0 upgrade
• #2726 — per-source: scope Info page data to active source
• #2725 — per-source: route scheduler restarts + autoWelcome tokens to the right source
• #2722 — per-source: Auto Announce Send Now + Virtual Node bootstrap and scoping

CI / DevOps

• #2742 — isolate api-exercise test from live dev volumes

Dependencies

• #2739 — bump puppeteer from 24.40.0 to 24.41.0
• #2737 — bump production-dependencies group with 15 updates
• #2736 — bump development-dependencies group with 3 updates

Release

• #2748 — bump version to 4.0.0-beta7

Issues Resolved

• #2743 — Node coordinates and favoriteLocked status overwritten by telemetry after restart
• #2741 — Successful traceroute makes last message in chat disappear
• #2731 — Connection Status card shows incorrect/stale Node Address
• #2730 — Auto Responder force DM
• #2724 — MM 4.0.0-beta5 how to enable virtual node?
• #2719 — Virtual Node not working after update to MM 4

Upgrade Notes

Upgraders from 3.12 → 4.0 benefit from #2740 migration hardening around the legacy nodes(nodeNum) foreign key. No manual action required.

Full Changelog: v4.0.0-beta6...v4.0.0-beta7

🚀 MeshMonitor v4.0.0-beta7

📦 Installation

Docker (recommended):

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

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