MeshMonitor v4.6.2-1

Hotfix re-publishing the v4.6.2 multi-arch Docker manifest. The v4.6.2 release pipeline succeeded for linux/amd64 and linux/arm64 but failed on linux/arm/v7 because [email protected] (bumped in #3071, shipped in v4.6.2) attempts to download a Chrome browser binary during npm postinstall and Chrome has no armv7 build — npm install aborted before the Dockerfile got any further.

No application-code changes. If you're on amd64 or arm64, v4.6.2 and v4.6.2-1 are functionally identical and you can stay on v4.6.2.

Fix

• #3096 fix(docker): skip puppeteer browser download on armv7 build — sets PUPPETEER_SKIP_DOWNLOAD=true on the armv7 npm install step. Puppeteer is a devDependency used only by CI tests; runtime armv7 images don't need the browser binary at all.

Who should upgrade

• armv7 (Raspberry Pi 2/3 32-bit) users — pull :v4.6.2-1 (or :latest); v4.6.2's armv7 image was never published.
• amd64 / arm64 users — no action required; v4.6.2 already covers you.

Full Changelog: https://github.com/Yeraze/meshmonitor/compare/v4.6.2...v4.6.2-1

🚀 MeshMonitor v4.6.2-1

📦 Installation

Docker (recommended):

docker run -d \
  --name meshmonitor \
  -p 8080:3001 \
  -v meshmonitor-data:/data \
  ghcr.io/Yeraze/meshmonitor:4.6.2-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.