Skip to content

[rust-LIN-06] Safety-case artifacts pinned to v0.2.0 while the crate ships v0.4.1 #32

Description

@SoundMatt

Location

BOUNDARY_DIAGRAM.md, DO178C_ALIGNMENT.md, SAFETY_MANUAL.md, SAFETY_PLAN.md, and safety-case.md — all titled/scoped to "rust-LIN v0.2.0".

Problem

Cargo.toml currently ships version = "0.4.1", but the entire safety-case document set (boundary diagram, DO-178C alignment, safety manual, safety plan, and the safety case itself) is titled and scoped to v0.2.0. DO178C_ALIGNMENT.md's baseline table even stops at v0.2.0 in its list of tagged releases. A safety case that doesn't cover the version actually being shipped isn't valid evidence for that shipped version — two minor releases' worth of changes (v0.3.x, v0.4.x) currently have no safety-case coverage at all.

Suggested fix

Bump the version referenced in all five safety artifacts to match the currently released version, and record what changed in the delta between v0.2.0 and the current release (new modules, new requirements, new hazards, etc.). Add a CI check that fails if the safety-artifact version strings don't match Cargo.toml.


Filed from the 2026-07-29 ecosystem audit register; independently re-verified against current HEAD before filing.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions