This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
Affected surfaces
Summary
AI summaryFixed auto‑responder Cyrillic parameter mangling by preserving Unicode during extraction.
Full changelog
What's Changed
Bug Fixes
-
fix: packet monitor infinite scroll and duplicate rows (#2259)
- Added viewport height constraint so the virtualizer properly constrains rendering
- Replaced broken IntersectionObserver with virtualizer-based scroll detection
- Deduplicated packets by ID to prevent overlap from polling refetch offset shifts
- Closes #2254
-
fix: security page crashes when Drizzle schema has columns missing from DB (#2257)
- Added try/catch fallback to raw SQL when Drizzle query fails due to missing columns
- Prevents crash when migration 084 hasn't run yet
-
fix: OSM tiles blocked by missing Referer header (#2261)
- Changed Helmet's Referrer-Policy from
no-referrertostrict-origin-when-cross-origin - OSM tile servers require a Referer header per their usage policy
- Closes #2260
- Changed Helmet's Referrer-Policy from
-
fix: auto-responder Cyrillic params mangled by homoglyph normalization (#2262)
- Homoglyph normalization was replacing some Cyrillic chars with Latin equivalents in extracted parameters, breaking geocoding APIs
- Now extracts parameters from original message text, preserving full Unicode
- Closes #2258
Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v3.9.2...v3.9.3
🚀 MeshMonitor v3.9.3
📦 Installation
Docker (recommended):
docker run -d \
--name meshmonitor \
-p 8080:3001 \
-v meshmonitor-data:/data \
ghcr.io/Yeraze/meshmonitor:3.9.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]