NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
Truly non-blocking, async Windows serial port I/O for Dart — backed by a Rust native library using overlapped Win32 I/O (no polling, no busy-wait).
Last release today
25 Oct 2026
Ships fairly regularly
a new release about every 2 months
Nearly every release is documented
notes for 5 of 5 stable releases
Nothing withdrawn
no release was ever pulled
3 months old
5 releases · first in 2026
One column per month.
Widen code_assets to >=1.0.0 <3.0.0 so BoltFFI 0.31 consumers (code_assets ^2) can resolve alongside this package.
Widen code_assets to >=1.0.0 <3.0.0 so BoltFFI 0.31 consumers
(code_assets ^2) can resolve alongside this package.
code_assets to >=1.0.0 <3.0.0 (was <2.0.0) so projects that pull code_assets 2.x — for example BoltFFI 0.31-generated Dart packages — can resolve alongside this package. hooks stays >=1.0.0 <3.0.0. Verified dart pub get against both code_assets 1.x and 2.x, and that hook/build.dart still registers the prebuilt DLL under code_assets 2.Widen hooks to >=1.0.0 <3.0.0 and code_assets to >=1.0.0 <2.0.0 (previously ^2.0.2/^1.2.1), so this package no longer forces a hooks: ^2.x constraint
hooks to >=1.0.0 <3.0.0 and code_assets to >=1.0.0 <2.0.0 (previously ^2.0.2/^1.2.1), so this package no longer forces a hooks: ^2.x constraint on projects that also depend on other packages still pinned to hooks: ^1.x. Verified against the oldest allowed pairing (hooks 1.0.0 + code_assets 1.0.0, the lowest versions matching this package's sdk: ^3.9.0 floor) — code_assets >=1.2.0 requires hooks ^2.0.0 internally, so both constraints had to widen together.Explicitly declare platforms: windows in pubspec.yaml so pub.dev shows this as a Windows-only package instead of inferring support for Android/iOS/Lin
platforms: windows in pubspec.yaml so pub.dev shows this as a Windows-only package instead of inferring support for Android/iOS/Linux/macOS from static analysis.Add more examples (basic usage, concurrent read/write, error handling).
Initial release: list, open, read (with timeout), write, drain, configure, close.
list, open, read (with timeout), write, drain, configure, close.Your coding agent can read these notes before it upgrades. Set up the MCP server →