MeshMonitor v4.12.1

A hotfix for a startup-breaking regression in 4.12.0.

🐛 Fixed

• Startup crash when upgrading to 4.12.0 (#3804, #3805) — On installs with MQTT channel permissions, migration 103 could fail with UNIQUE constraint failed: channel_database_permissions.user_id, channel_database_permissions.channel_database_id and crash the app on every start, leaving it unbootable. When consolidating duplicate MQTT channels, the migration now removes conflicting permission rows before reassigning them to the keeper channel (SQLite, PostgreSQL, and MySQL — the latter via a derived-table subselect). A regression test covers the collision case.

Anyone who hit the crash on 4.12.0 can upgrade straight to 4.12.1. (If you previously hand-patched the compiled migration as a workaround, that's fine — the migration is idempotent.)

Thanks to @BeerMan81 for the detailed report and root-cause analysis.

Full changelog: v4.12.0...v4.12.1

🚀 MeshMonitor v4.12.1

📦 Installation

Docker (recommended):

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

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