Tags: zooai/node
Tags
Fix Zoo Node v1.1.11 build - downgrade rmcp to 0.6 The zoo-tools-primitives/mcp_methods.rs code is written for rmcp 0.6 API. Someone previously upgraded to rmcp 0.8 but didn't update the code to match. This fix downgrades rmcp back to 0.6 to match the existing code implementation. Technical details: - rmcp 0.8 changed API structure (no client module, different transport interface) - Zoo's MCP code uses rmcp 0.6 API patterns (McpClient, ChildProcessTransport) - Hanzo has hanzo-mcp 1.1.10 which works with rmcp 0.8 (future migration target) Fixes: - All zoo_message_primitives resolution errors - rmcp client module not found errors - rmcp transport API incompatibility errors This enables Zoo Node v1.1.11 to build successfully on all platforms.
v1.1.34: Add crate metadata for crates.io publishing Added to workspace.package: - license = "MIT" - repository = "https://github.com/zooai/node" - homepage = "https://zoo.ai" - keywords and categories Added to all crate Cargo.toml files: - description (crate-specific) - license = { workspace = true } - repository = { workspace = true } - homepage = { workspace = true } Crates ready for: cargo publish
v1.1.33: Remove build.rs (zoo-node doesn't need asset copying) ERROR: build.rs:4 - use of unresolved module zoo_tools_runner FILE: zoo-bin/zoo-node/build.rs ROOT CAUSE: build.rs calls zoo_tools_runner::copy_assets::copy_assets We removed zoo_tools_runner from [build-dependencies] in v1.1.32 But build.rs file still existed and tried to use it FIX: Deleted zoo-bin/zoo-node/build.rs entirely - Zoo-node doesn't need to bundle/copy tool runner resources - Assets are handled at runtime, not build time - Hanzo-node needs build.rs for bundling, zoo-node doesn't THIS IS THE FINAL FIX - no build script = no build-time dependencies!
v1.1.32: Remove zoo_tools_runner from build-dependencies ERROR: Build script panic - failed to move UV binary: No such file or directory FILE: hanzo-node/hanzo-libs/hanzo-tools-runner/src/copy_assets.rs:322 ROOT CAUSE: zoo_tools_runner in [build-dependencies] runs build script The build script tries to copy binaries from ./hanzo-tools-runner-resources/ but this path doesn't exist in zoo-node context FIX: Removed zoo_tools_runner from [build-dependencies] - Runtime dependency in [dependencies] is sufficient - We don't need to run the resource-copying build script - Zoo-node uses runtime tools, not build-time bundling THIS SHOULD BE THE FINAL FIX!
v1.1.31: Add missing zoo_tools_runner dependency to zoo-non-rust-code ERROR: use of unresolved module or unlinked crate zoo_tools_runner FILE: zoo-libs/zoo-non-rust-code/src/lib.rs:4 ROOT CAUSE: Cargo.toml had hanzo_non_rust_code but source code imports zoo_tools_runner FIX: Added zoo_tools_runner to dependencies in zoo-non-rust-code/Cargo.toml This completes all dependency declarations for the wrapper pattern.
v1.1.30: Fix type mismatch - use HanzoNodeLocation directly (type alias) ERROR: Type mismatch - expected HanzoNodeLocation, found ZooNodeLocation ROOT CAUSE: We created a NEW struct ZooNodeLocation instead of using hanzo's type FIX: Changed ZooNodeLocation to be a type alias: pub use hanzo_tools_runner::tools::hanzo_node_location::HanzoNodeLocation as ZooNodeLocation BENEFIT: - No type conversion needed - Same underlying type (compile-time alias) - Maintains zoo naming convention for API compatibility - Zero runtime overhead This is the CORRECT wrapper pattern - re-export with alias, don't duplicate.
v1.1.29: Fix field name mismatch - zoo_node_location → hanzo_node_loc… …ation ERROR: DenoRunnerOptions and PythonRunnerOptions don't have 'zoo_node_location' field FIX: Changed to 'hanzo_node_location' (correct hanzo API field name) The hanzo_tools_runner structs use hanzo_node_location, not zoo_node_location. Our wrapper struct ZooNodeLocation is correctly defined, but we were using the wrong field name when constructing the runner options. Changed in zoo-tools-primitives/src/tools: - deno_tools.rs: 2 occurrences - python_tools.rs: 1 occurrence This completes the zoo-tools-runner wrapper implementation.
v1.1.28: Fix cyclic dependency in zoo-non-rust-code ERROR: zoo_non_rust_code depended on itself (line 11) FIX: Changed to hanzo_non_rust_code (correct dependency) The cleanup script in v1.1.27 accidentally changed hanzo_non_rust_code to zoo_non_rust_code, creating a cyclic dependency. This is the final fix for the zoo-tools-runner wrapper approach.
PreviousNext