This release fixes issues for SREs watching stability and regressions.
Published 3mo
Monitoring & Metrics
✓ No known CVEs patched
✓ No known CVEs patched in this version
Topics
meshcore
meshtastic
mqtt
Summary
AI summaryFixed telemetry packetId overflow on PostgreSQL/MySQL and pre-populated MeshCore connection form from env vars.
Full changelog
What's Changed
Bug Fixes
- Upgrade telemetry packetId to BIGINT for PostgreSQL/MySQL (#1967) - Fixes #1964
- Resolve MySQL/PostgreSQL node loss during init config sync (#1965)
- Pre-populate MeshCore connection form from env vars (#1963) - Fixes #1960
- Replace GPL session store and add MySQL URL detection (#1961)
- Add processing delays to config import for reliable LoRa preset application (#1958)
- Add DHCP client and networking service enablement to LXC template (#1956)
Tests
- Add database backing consistency test across SQLite/PostgreSQL/MySQL (#1966)
- Fix flaky DB backing consistency test node count check (#1968)
Other
- Fix inaccuracies in Proxmox LXC deployment guide (#1957)
- Translations update from Hosted Weblate - Russian (#1959)
Issues Resolved
- #1964 - Telemetry insert failures on PostgreSQL due to packetId overflow
- #1960 - MeshCore connection settings not pre-populated from env vars
🚀 MeshMonitor v3.6.4
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.6.4
🧪 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]