Skip to content

RCH Rust v3.0.0-preview.6

Pre-release
Pre-release

Choose a tag to compare

@brothercorvo brothercorvo released this 02 Jul 18:51
3546666

RCH Rust v3.0.0-preview.6 Release Notes

This prerelease refreshes the Rust RCH 3.0.0 preview line after v3.0.0-preview.5.

Python 2.9.x remains the stable maintenance line on rch-python; this is a Rust preview intended for validation of the 3.0 runtime, packaging, migration, LXMF, TAK integration, and local operator desktop path.

Runtime Requirement

RCH Rust 3.0 requires a running LXMF-rs reticulumd instance. The server package includes the RCH server, TAK service, shared UI, and service templates, but it does not replace the Reticulum/LXMF daemon. Start and configure reticulumd first, then run RCH with its ZeroMQ SDK command and response endpoints pointed at that daemon. Without reticulumd, RCH can serve its northbound API/UI, but Reticulum messaging, peer discovery, delivery receipts, and announce operations will not work.

Highlights Since preview.5

  • Added the first-run setup wizard for hub name, TCP bootstrap interface selection, remote access password, and operator-chosen kill-switch PIN enrollment.
  • Added the Configure > Kill Switch UI with dual-arm authorization, PIN verification, confirmation, and purge progress visualization.
  • Added Rust backend kill-switch purge support for SQLite state, configuration files, Reticulum identity/runtime artifacts, and uploaded attachment blobs.
  • Hardened purge safety by stopping runtime workers, locking persistence during and after purge, avoiding broad database-extension glob deletion, and limiting artifact deletion to explicit paths plus known runtime filenames.
  • Added Reticulum identity display/creation during first-run setup and REM-style TCP community server choices for bootstrap configuration.
  • Updated the Rust workspace to the LXMF-rs 0.6.0 line and refreshed dependency pins for the shared Rust crates.
  • Preserved post-setup confidentiality by redacting local filesystem paths from unauthenticated setup status responses.

Validation

Local validation before release:

  • cargo fmt --all -- --check
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test --workspace

GitHub validation passed before publishing:

  • PR #205 Rust PR Quality Control: Format, Clippy, Workspace Tests, Release Builds, and Dependency Audit.
  • PR #205 Rust workspace: release-readiness gate.
  • main Rust workspace: release-readiness gate on commit 354666620f4be0a6a979d136a956e244401330de.

The GitHub release package workflow is expected to attach release artifacts after the prerelease publish event completes.

Known Boundaries

  • This remains a preview/alpha release, not stable v3.0.0.
  • Operator packaging and desktop bundles are still preview artifacts while field feedback settles.
  • External TAK, Reticulum/RMAP, and live-device gates remain optional evidence for this preview unless a blocker appears during release validation.
  • Keep Python parity and Rust transition gaps tracked in the repository release/readiness documentation.