Skip to content

Yeraze/meshmonitor

v4.11.5 Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 1mo Monitoring & Metrics
βœ“ No known CVEs patched
Read the diff β†’ Tool health β†’ What is this tool? β†’

✓ No known CVEs patched in this version

Topics

meshcore meshtastic mqtt

Affected surfaces

breaking_upgrade

Summary

AI summary

Updates πŸ”΄ Hotfix, πŸš€ MeshMonitor v4.11.5, and retracted across a mixed release.

Full changelog

πŸš‘ Hotfix release β€” supersedes v4.11.4 (retracted)

v4.11.4 was pulled because migration 033 crashed startup on PostgreSQL and on fresh installs with column "sourceId" does not exist (#3657). v4.11.5 fixes that and carries everything that was in v4.11.4.

If you ran v4.11.4, update to v4.11.5. The boot crash is resolved.

πŸ”΄ Hotfix (#3657)

  • Migration 033's channel_database backfill is now guarded on the legacy sourceId column existing (it's global-by-design β€” migration 021 no longer adds it and 063 drops it). Fixes the PostgreSQL / fresh-install boot crash introduced in v4.11.4.

Also included (from the retracted v4.11.4)

Critical

  • PostgreSQL boot-loop fix (tables can have at most 1600 columns) (#3639)

Features

  • MeshCore role icons in the map + DM node lists (#3647)
  • MeshCore favorites pinned to the top of the DM list (#3620)
  • Marker spiderfying for overlapping nodes on Map Analysis + Unified maps (#3612)
  • Channel "overshadow" warning for same-key/different-name Channel Database entries (#3644)
  • Traceroute packetId for cross-source correlation (#3623)

Fixes

  • Node disconnects / TX failures since 4.11.x (#3637)
  • Custom-LoRa-config primary channel mislabeled "LongFast" (#3644)
  • TCP reconnect shows the real per-source address (#3611)
  • Fictitious traceroute segments removed; incoming traceroutes visible (#3622)
  • MeshCore hashtag #channel secrets over plain HTTP-via-IP + at save time (#3606, #3607)
  • MeshCore Last Heard preserved across reconnect (#3645)
  • MeshCore new nodes populate fully when heard live (#3646)
  • Unified-map neighbor lines follow the merged marker (#3642)
  • Adaptive node-type filter per source protocol (#3610)
  • Saner single-anchor position-estimate uncertainty (#3616)

πŸš€ MeshMonitor v4.11.5

πŸ“¦ Installation

Docker (recommended):

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

πŸ§ͺ 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.

Breaking Changes

  • v4.11.4 was retracted due to a breaking migrationβ€―033 that crashed startup when the legacy column `sourceId` did not exist; this release corrects the issue and supersedes v4.11.4.

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

Track Yeraze/meshmonitor

Get notified when new releases ship.

Sign up free

About Yeraze/meshmonitor

All releases β†’

Related context

Earlier breaking changes

  • v4.13.0 Source‑scoped API endpoints now require an explicit `sourceId` parameter.
  • v4.13.0 Auto-Upgrade is retired; remove upgrade sidecar and related config.
  • v4.7.2 Route `destination` field now rejects non‑8‑hex nodeId or 64‑hex publicKey, returning HTTPβ€―400.

Beta — feedback welcome: [email protected]