device-kit ➜ device-envoy

⚠️ This crate has been renamed to device-envoy

What happened?

The device-kit crate was renamed to device-envoy for better clarity and to avoid naming conflicts.

How to update

Replace device-kit with device-envoy in your Cargo.toml:

[dependencies]
# Old:
# device-kit = "0.0.2"

# New:
device-envoy = "0.0.2-alpha"

Why the rename?

• Better name clarity: device-envoy better describes the crate's role as an "envoy" between your application and embedded devices
• Avoid conflicts: Prevents potential naming conflicts with other device-related crates
• Long-term stability: Establishes a clearer brand for the project

Links

• New crate: device-envoy
• Documentation: docs.rs/device-envoy
• GitHub: CarlKCarlK/device-envoy
• Migration guide: See the device-envoy README

About device-envoy

Build Pico applications with LED panels, easy WiFi, and composable device abstractions.

device-envoy explores application-level device abstractions in embedded Rust using the Embassy async framework. It focuses on building reusable, typed async APIs that hide timing, interrupts, channels, and shared state inside each device.

Currently targeting Raspberry Pi Pico 1 and Pico 2 (ARM cores).