Tags: OverFlow636/river
Tags
build: release riverctl 0.1.22 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Release riverctl v0.1.14 - Add message streaming functionality
fix: Update dependencies to resolve tokio-tungstenite version conflict - Update freenet-stdlib from 0.1.13 to 0.1.14 - Update tokio-tungstenite from 0.26 to 0.27 in riverctl - Bump riverctl version to 0.1.11 - Update all workspace dependencies to latest compatible versions This fixes the compilation error users were experiencing when trying to install riverctl due to version mismatches in the dependency chain. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Release v0.1.10 - Fixed message propagation issue where room creators couldn't see messages from other participants - Room creators now automatically subscribe to their own rooms upon creation - This ensures all participants receive UPDATE notifications for new messages
Release v0.1.9 - Updated freenet-stdlib from 0.1.8 to 0.1.13 - Increased WebSocket timeouts for better network stability - PUT/GET operations: 2s → 10s - SUBSCRIBE operations: 1s → 5s - Code quality improvements - Added appropriate #[allow(dead_code)] annotations - Simplified struct initialization with Default trait - Fixed unused variable warnings - Improved error messages for timeout scenarios
riverctl v0.1.7 - Fixed architectural issue with GET operations using subscribe:true - GET and SUBSCRIBE operations are now properly separated - Fixed UI build error (river_common -> river_core imports) - Enables multi-user messaging to work properly The previous implementation attempted to use GET with subscribe:true, which requires performing sub-operations from within the main operation. This was never implemented in Freenet due to architectural constraints. This release separates GET and SUBSCRIBE into distinct operations, aligning riverctl with how the River web UI already works.
PreviousNext