Skip to content

3.2.1

Latest

Choose a tag to compare

@dfeen87 dfeen87 released this 05 Apr 15:23
· 2 commits to main since this release
23f1232

HLV‑RAPS v3.2.1 — Patch Release

Release Date: 2026‑04‑05
Scope: Documentation corrections and consistency fixes.
Code Changes: None.

This patch release resolves factual inconsistencies, stale references, and formatting issues introduced or left unresolved after the v3.2.0 hardening round. No source code, API, or architectural changes were made.


Documentation Corrections & Consistency Fixes

Version Alignment

  • CHANGELOG.md: Corrected incorrect VERSION file reference inside the [3.2.0] entry
    • (2.4.0)(3.2.0)
  • CITATION.cff: Updated year: 2025year: 2026 to match LICENSE copyright.
  • docs/TELEMETRY_DASHBOARD.md: Updated three stale v2.3/v2.3.0 references → v3.2/v3.2.0.
  • docs/contracts/TELEMETRY_STORAGE_CONTRACT.md: Updated contract header
    • (RAPS v2.3.0)(RAPS v3.2.0).

Broken File Reference

  • Fixed incorrect reference to docs/telemetry_dashboard_v2.3.md
    → Corrected to docs/TELEMETRY_DASHBOARD.md.

Quick Start Corrections

RTOS Demo

  • Removed misleading implication that hlv_rtos_demo is produced by the SIL CMake build.
  • Replaced with accurate prose clarifying it is a platform‑specific reference example with no standalone CMake target.

REST API Demo

  • Added correct build and run instructions:
    cmake -S examples/api_client -B build/api_demo
    cmake --build build/api_demo
    ./build/api_demo/rest_api_demo
    

curl Example

  • Corrected nonexistent endpoint:
    /api/status/health.

Formatting & Completeness Improvements

  • docs/architecture.md:

    • Added missing # System Architecture title.
    • Completed dangling sentence with correct path:
      src/common/types.hpp.
  • docs/sil_hil.md:

    • Wrapped ASCII architecture diagram in a code fence.
    • Fixed misaligned (SIL) and (HIL) labels for readability.

Summary

This release focuses exclusively on documentation accuracy, clarity, and consistency. All changes are non‑breaking and do not affect runtime behavior, APIs, or build outputs.