You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: WS peer UDS routing for bi-directional cross-machine mesh
Remote peers connected via WebSocket no longer trigger futile UDS
socket connections. Added hasRemotePeer() check — peers with an
active WS connection skip push.connect() and route via WS-first.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,11 @@ All notable changes to SLM Mesh will be documented in this file.
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
6
6
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
7
7
8
+
## [1.3.3] - 2026-05-22
9
+
10
+
### Fixed
11
+
-**WebSocket peer routing bug** — Remote peers connected via WS no longer trigger futile UDS socket connections. The broker now checks `hasRemotePeer()` before attempting UDS, and routes messages via WS for remote peers (WS-first, UDS fallback). Fixes bi-directional cross-machine messaging.
0 commit comments