This release adds 1 notable feature for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryFixed Show MeshCore toggle visibility and persistence, prevented fractional values in integer telemetry graphs.
Full changelog
What's Changed in v3.6.2
Bug Fixes
- fix: hide Show MeshCore toggle when disabled and persist its state - The "Show MeshCore" checkbox in the map Features panel was always visible regardless of
MESHCORE_ENABLEDsetting, and its state was never saved. Now properly hidden when MeshCore is disabled and persists across page loads. (#1940) - fix: prevent fractional values in integer telemetry graphs (#1939, #1936)
- fix: memoize map marker icons to prevent position update interference (#1938)
- fix: render emoji short names as HTML overlay on map markers (#1937, #1934)
- fix: add BASE_URL support to MeshCore API endpoints (#1935)
- fix: derive short name from last 4 hex chars of node ID to match Meshtastic convention (#1932, #1929)
- fix: position history endpoint nodeId parsing and pagination (#1931)
- fix: increase auto-responder and script test timeout from 10s to 30s - All automation script execution paths (auto-responder, timer, geofence, and the UI "Test" popup) now use a consistent 30-second timeout. (#1942)
New Features
- feat: add V1 API position history endpoint (#1930)
Database Migration
This release includes migration 074 which adds the show_meshcore_nodes column to user_map_preferences. This migration runs automatically on startup for SQLite, PostgreSQL, and MySQL.
Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.6.1...v3.6.2
🚀 MeshMonitor v3.6.2
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.6.2
🧪 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
About Yeraze/meshmonitor
All releases →Related context
Related tools
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]