Version History & Changelog
Relevant source files
The following files were used as context for generating this wiki page:
The tauri-plugin-serialplugin project maintains a detailed record of its evolution, documenting transitions from initial implementation to a robust, cross-platform serial communication tool. This version history tracks the introduction of core features, platform-specific enhancements for Android and Desktop, and critical bug fixes that ensure reliable hardware interaction.
The changelog serves as the primary ledger for developers to understand API breaking changes, such as the shift from event-based to synchronous reading, and the expansion of the plugin's capabilities to include binary data handling and automated port discovery. Sources: CHANGELOG.md, package.json:3
Release Timeline and Evolution
The project follows semantic versioning, with major releases defining significant architectural shifts. The transition to the 2.x branch marked the adoption of the Tauri v2 plugin architecture.
Key Version Milestones
| Version | Date | Primary Focus |
|---|---|---|
| 2.22.0 | 2026-03-21 | Android Lifecycle & Data Coalescing |
| 2.21.0 | 2025-10-11 | Disconnection Event Emission |
| 2.20.0 | 2025-10-11 | Centralized Logging Module |
| 2.12.0 | 2025-06-12 | Test Mode & Simulation |
| 2.8.0 | 2025-01-30 | Binary Data Support |
| 2.6.0 | 2025-01-14 | Managed Ports Functionality |
| 2.1.0 | 2024-11-01 | Extended Serial Control Methods |
Sources: CHANGELOG.md:10-300, package.json:3
Version 2.22.0: Android Optimization
The latest stable release focused heavily on the Android implementation, introducing advanced lifecycle management and data throughput optimizations.
Architectural Improvements
- Lifecycle Integration: The
SerialPluginnow registersActivityLifecycleCallbacks. This ensures that when the host Android Activity is destroyed,SerialPortManager.cleanup()is automatically invoked to close USB ports and shut down IO executors. - Data Coalescing: To prevent frontend event flooding, incoming serial data is coalesced using a
BufferedEmitterandSerialByteAccumulator. The flush interval is configurable viaserialDataFlushIntervalMs. - HW Buffer Purging: The
clearBuffercommand was mapped topurgeHwBuffersin theusb-serial-for-androidlibrary.
Sources: CHANGELOG.md:10-25, android/README.md:10-15
The diagram illustrates the automatic cleanup triggered by the Android Activity lifecycle and the data coalescing pipeline. Sources: CHANGELOG.md:12-15, android/README.md:12
Version 2.8.0 - 2.12.0: Feature Expansion
This period saw the introduction of complex features required for industrial-grade serial applications.
Binary and Test Capabilities
- Binary I/O: Added
read_binaryandwrite_binarycommands, allowing the plugin to handle non-textual protocol data. Sources: CHANGELOG.md:160-170 - Simulation Mode: Version 2.12.0 introduced a test mode for simulating serial port behavior, enabling developers to test frontend logic without physical hardware. Sources: CHANGELOG.md:130-135
- Managed Ports: A new command
managed_portswas added to track and list all ports currently opened and active within the plugin's state. Sources: CHANGELOG.md:180-195
Version 2.1.0 - 2.2.0: Protocol Control
These versions significantly expanded the control API, moving beyond simple read/write to full serial line state management.
Control Signal Support
The plugin added support for hardware flow control and signal state reading:
- Write Signals:
write_request_to_send(RTS) andwrite_data_terminal_ready(DTR). - Read Signals:
read_clear_to_send(CTS),read_data_set_ready(DSR),read_ring_indicator(RI), andread_carrier_detect(CD). - Buffer Management:
bytes_to_read,bytes_to_write, andclear_bufferwere implemented to provide parity with native serial APIs.
Sources: CHANGELOG.md:240-265, src/lib.rs:145-165
Version History Summary
The project evolution shows a clear trajectory:
- Phase 1 (2.0.x): Foundation and basic cross-platform support.
- Phase 2 (2.1.x - 2.3.x): Comprehensive API expansion for protocol control.
- Phase 3 (2.4.x - 2.12.x): Robustness improvements, binary data support, and testing utilities.
- Phase 4 (2.13.x - 2.22.0): Advanced Android support, logging systems, and optimized event handling.
Sources: CHANGELOG.md, Cargo.toml:3-10, debug.md:5-20
The continuous refinement of the Android implementation, specifically handling the nuances of usb-serial-for-android and the Android Activity lifecycle, distinguishes recent versions as a production-ready solution for mobile serial communication. Sources: android/README.md, debug.md:100-115