RustQueue 0.10.1

RustQueue 0.10.1

RustQueue 0.10.1 fixes queue memory and recovery failures, NSQ heartbeat timing,
completed recovery status, TLS CLI startup, and producer-proxy rollout continuity.
The optional WebSocket live subscription introduced in 0.10.0 remains default-off.

Queue memory and recovery

• Sealing releases unused metadata and record-location buffer capacity before
  returning cache credits. Cold Topics no longer retain their former active buffers.
• Delayed-message deadlines stay in queue metadata. Statistics use segment ranges
  and bounded pages, and consumer scans keep one rewind position per Channel.
• Recovery compacts older DPUB scan entries one Channel at a time. Explicit REQ
  deadlines and attempts remain durable; lost relaxed positions are fenced before
  absent state is removed and are never reused.
• A node-wide in-flight message limit bounds empty-message and consumer-session
  metadata as well as the existing payload-byte budget.

Rust statistics APIs return Result so metadata read failures can propagate.
HTTP statistics/metrics fail and isolate uncertain storage rather than returning
successful partial counts. Rust callers must handle these errors; successful
HTTP response schemas remain unchanged.

Runtime and Console fixes

• NSQ heartbeat send timing advances after awaited response writes complete.
• Completed Operator recovery stops using the expired recovery deadline while
  waiting for a replacement Broker to become Ready.
• The CLI installs its TLS crypto provider before parsing commands.
• Producer-proxy DaemonSets retain an endpoint while rolling.
• Recreating a deleted Topic applies the requested delivery mode and TTL instead
  of inheriting its old policy; choosing reliable delivery clears the old TTL.
• Console navigation supports mobile menu dismissal and focus restoration, and
  snapshot failures remain visible to the user. The footer reads the packaged
  version instead of displaying a hard-coded previous release.

Upgrade

The v7 data format, RCC7 Channel checkpoints and RQTMv2 metadata remain compatible.
No Topic data migration is required. Apply the CRDs before upgrading an existing
Operator installation, then update Broker and Operator images to 0.10.1.

Release assets

• rustqueue-0.10.1-linux-x86_64.tar.gz
• rustqueue-0.10.1-linux-aarch64.tar.gz
• rustqueue-0.10.1-source.tar.gz
• rustqueue-0.10.1.tgz
• SHA256SUMS-0.10.1

The production-gate workflow builds the release from the commit on main, runs
core, compatibility, UI, Helm and fuzz checks, builds both Linux architectures,
and verifies the published asset checksums. Local scoped runtime checks are
recorded separately from throughput and latency calibration; memory observations
are not a calibrated performance comparison.
The Linux performance workflow gives Broker and load generator separate CPU
sets within their existing two-CPU limits, and records the effective placement.
Calibration still gates the comparison using the original measurement windows
and spread thresholds.