This release adds 1 notable feature for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
Summary
AI summaryFixed PostgreSQL/MySQL startup failure caused by incorrect backup_history schema.
Full changelog
🔧 Hotfix Release
This hotfix resolves a startup failure on PostgreSQL/MySQL backends introduced in v3.2.1.
Bug Fixes
- Fixed PostgreSQL/MySQL startup failure - Migration 056 (backup_history column fix) now properly supports PostgreSQL and MySQL databases. The migration runs before schema initialization to fix tables with incorrect schemas before index creation is attempted. (#1586)
Technical Details
The previous fix (v3.2.2) only addressed SQLite databases. PostgreSQL/MySQL databases with existing backup_history tables that had incorrect schemas would fail at startup with:
error: column "timestamp" does not exist
routine: 'ComputeIndexAttrs'
This release adds runMigration056Postgres() and runMigration056Mysql() functions that:
- Run BEFORE the schema SQL is executed
- Check if the
backup_historytable has the correct columns - Recreate the table with the correct schema if needed
Pull Requests
- #1586 - fix(migration): add PostgreSQL/MySQL support to migration 056
Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.2.2...v3.2.3
Proxmox LXC Template
This release includes a Proxmox-compatible LXC container template for MeshMonitor.
Installation
- Download the
.tar.gztemplate file - Verify the SHA256 checksum (optional but recommended)
- Upload to your Proxmox server:
scp meshmonitor-*.tar.gz root@proxmox:/var/lib/vz/template/cache/ - Create a new LXC container from the template via Proxmox web UI
- Configure
/etc/meshmonitor/meshmonitor.envwith your Meshtastic node IP - Start the container and access the web UI on port 8080
Documentation
See the Proxmox LXC Deployment Guide for detailed instructions.
Limitations
- Auto-upgrade feature is not supported in LXC deployments
- Manual updates required (download new template for each version)
- Community-supported (Docker remains the primary deployment method)
🚀 MeshMonitor v3.2.3
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.2.3
🧪 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]