Repository navigation
Releases: Pnex/pnex-rs
Releases · Pnex/pnex-rs
Release list
PNeX v0.1.0-beta.7
0.1.0-beta.7 — 2026-10-07
Security
- Bound the pinned CA decode, per-chip CA limit (SEC-16) (6d7b258)
Bug fixes
- builds: Tier quotas only in saas, a build no longer counts itself (7deeefa)
- media: Walk inside splats with the keyboard (e738e7a)
Documentation
- Demo findings O35–O40 (d1882b4)
Full diff: v0.1.0-beta.6...v0.1.0-beta.7
Nightly (main d1882b4)
Latest green main build (d1882b4). Desktop apps for Linux x86_64 / aarch64 and Windows x86_64, Android APK (arm64, debug-signed). Not a stable release.
PNeX v0.1.0-beta.5
Highlights
- Device (write) drives custom firmware commands (D146). A command declared with
pnex.onCommand()in your own firmware now shows up in the Device (write) node next to the output pins; the wired value reaches the firmware inargs["value"]. A dashboard colour, option or setpoint control goes to a command (a pin would refuse it). Command values are capped at 512 bytes. - New tutorials built on this release: See a room's temperature on a dashboard and Drive the board's RGB LED from a dashboard.
Fixes
- Flows: a node wired after Device (write) received nothing (its two outputs were not padded at deploy).
- Flows: picking the same device again in Device (write) / Device (read) cleared its wires; a redeploy then silently wrote nothing.
- Dashboards: "Stale after" now greys home cards out; a value widget next to a 24 h chart of the same series no longer looks stale.
- Dashboards: widgets added on a desktop canvas take the first free area instead of stacking; "From a device" no longer hides the metric name; a saved source stays listed when its device was silent for 24 h.
Known issue
- A custom firmware command is very rarely not applied by the board (2 cases seen, none in ~230 attempts since). Pressing the card again applies it. Tracked in
docs/architecture/custom-firmware.md§14 (item 6).
Full Changelog: v0.1.0-beta.4...v0.1.0-beta.5