Skip to content

v0.5.0

Choose a tag to compare

View all tags
@Oceanswave Oceanswave released this 04 Feb 05:01
· 4 commits to main since this release
v0.5.0
cf6078f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's Changed

Changed

  • Slim node capabilities — node now advertises only location.get + system.run to the gateway (was 29 individual commands); all 34 handlers remain available via system.run meta-dispatch, reducing handshake payload and simplifying capability negotiation
  • Explicit send_connected() lifecycle — node.connected event is now sent explicitly after connect_with_backoff() and after successful reconnection, replacing the implicit first-frame trigger; CLI callers show a warning if the lifecycle event fails while the connection itself succeeded
  • send_connected() returns bool — callers can now detect lifecycle event failure; both openclaw bridge and serve commands display a yellow warning when the event fails to send
  • Separated reconnect error handling — _maybe_reconnect() now handles connection failure and lifecycle event failure independently; a failed node.connected no longer incorrectly doubles the reconnect backoff timer

Added

  • on_reconnect gateway callback — GatewayClient accepts an on_reconnect callback invoked after the receive loop successfully reconnects, ensuring node.connected is sent on every reconnection (not just the initial connect)
  • system.run activity logging — dispatcher logs the resolved inner method when routing through system.run, so operational logs show system.run → door.lock instead of just system.run

Fixed

  • send_connected() false-positive logging — no longer logs "Sent node.connected event" when the gateway is disconnected (the event was being silently dropped by send_event())
  • OpenClawPipeline.dispatcher typing — changed from Any to CommandDispatcher for static analysis support

Full Changelog: v0.4.0...v0.5.0

Assets 2
Loading