chore: bump hosts to 0.4.0

The host crates ship breaking changes (log format v2, flush and
set_wall_clock, the tines::serve signature, tines-core 1) that can't go
out as the already-released 0.3.0 (1.0 review S13). tines-core stays
1.0.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-22 08:44:09 -07:00
co-authored by Claude Opus 5.5
parent 3db1e97545
commit 8c97963364
4 changed files with 11 additions and 11 deletions
+3 -3
View File
@@ -21,12 +21,12 @@ ros2 = ["dep:rclrs", "dep:ros-env", "dep:tines"]
[dependencies]
tines-core = { path = "../tines-core", version = "1" }
tines-store = { path = "../tines-store", version = "0.3.0" }
tines-bt = { path = "../tines-bt", version = "0.3.0" }
tines-store = { path = "../tines-store", version = "0.4.0" }
tines-bt = { path = "../tines-bt", version = "0.4.0" }
# The host's wall-clock abstraction (`HostClock`) and the trusted-time state
# machine it drives. Only needed behind the `ros2` feature — `TinesNode` is the
# only consumer and that is compiled only with `ros2` — so keep it optional.
tines = { path = "../tines", version = "0.3.0", optional = true }
tines = { path = "../tines", version = "0.4.0", optional = true }
rclrs = { version = "0.8", optional = true }
# ros_env provides the ROS 2 message types (std_msgs, including
# UInt8MultiArray) by include!()ing the generated crates from