lfg2025
released this
2026-05-17 22:40:50 +00:00
| 404 commits to main since this release
Release notes\n\n- Mesh networking now supports Meshtastic radios over the Meshtastic serial API in addition to existing MeshCore Companion USB radios.\n- The mesh listener now probes preferred and auto-detected serial paths for both MeshCore and Meshtastic firmware, preserving the existing reconnect loop so unplug/replug and firmware hot-swap behavior stays consistent.\n- Meshtastic text packets are translated into the existing Archipelago mesh frame pipeline, so current RPC handlers, transport routing, message storage, typed-message decoding, and UI state continue to work without a separate frontend path.\n- Meshtastic node information is surfaced as normal mesh contacts using stable synthetic public keys derived from Meshtastic node numbers, allowing peer refresh and message attribution to reuse existing MeshCore contact handling.\n- Outbound Archipelago mesh messages can now be sent through Meshtastic as channel text packets using the same command path used by MeshCore channel broadcasts.\n- Device status now reports the detected firmware family as meshcore or meshtastic from the shared listener abstraction.\n- Radio udev rules now include USB CDC ACM serial devices (ttyACM*) alongside CP2102, CH340, and FTDI adapters so Meshtastic boards are more likely to appear through the stable /dev/mesh-radio symlink.\n- Host nginx now serves /assets/* hashed frontend chunks as immutable static files with a hard 404 on misses instead of falling back to index.html, preventing strict MIME errors when a browser has a stale pre-update HTML shell.\n- The SPA HTML shell and service-worker files now revalidate on every load, reducing stale frontend references after OTA updates.\n- OTA runtime promotion now installs the bundled nginx-archipelago.conf into /etc/nginx/sites-available/archipelago and reloads nginx after a successful config test, so frontend cache/fallback fixes reach existing nodes without a manual deploy.\n\n## Validation\n\n- cargo check -p archipelago\n- cargo build -p archipelago --bin archipelago --release\n- npm run build\n- scripts/check-release-manifest.sh\n\n## Known limitation\n\n- Live SSH testing against 100.70.96.88 was not completed because temporary public-key authentication was rejected on the target.\n
Downloads