fix: migrate .fusa-hara.json to x-FuSa v1.13/v1.14 HARA schema, pin c-FuSa to v0.5.46 - #92
Merged
Merged
Conversation
…-FuSa to v0.5.46
c-FuSa v0.5.46 started enforcing a stricter HARA schema (HARA002/HARA003)
per ISO 26262-3: hazards now need a nested risk{severity,exposure,
controllability,asil} object instead of flat fields, and a safetyGoals[]
reference array instead of a free-text safety_goal string. Migrated all
10 hazards and added the formal safetyGoals registry (SG-001..SG-009)
that HARA004 checks against, deriving each goal's ASIL as the max ASIL
of the hazards it addresses per standard practice.
Also pins c-FuSa to v0.5.46 in ci.yml/release.yml instead of cloning its
default branch unpinned -- this is exactly how this regression happened
(an unrelated upstream c-FuSa change silently broke main's cfusa check
with no corresponding commit in this repo to explain why), matching the
same fix being applied ecosystem-wide for every x-FuSa tool reference.
Verified: cfusa check (built from the pinned v0.5.46 tag) now reports
0 errors (was 20: 10x HARA002, 10x HARA003).
Fixes #89
Signed-off-by: Matt <47545907+SoundMatt@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #89 — c-FuSa v0.5.46 started enforcing a stricter HARA schema (HARA002/HARA003) per x-FuSa spec v1.13/v1.14 conformance. This repo's
.fusa-hara.jsonused the old flat shape and started failingcfusa checkwith 20 errors on every PR, unrelated to whatever that PR actually changed.risk{severity,exposure,controllability,asil}nested object andsafetyGoals[]reference-array shape.safetyGoalsregistry (SG-001..SG-009) that HARA004 checks against — each goal's ASIL derived as the max ASIL across the hazards it addresses, per standard ISO 26262-3 practice.v0.5.46inci.yml/release.ymlinstead of cloning its default branch unpinned — this is exactly how the regression happened silently (an unrelated upstream c-FuSa change brokemain'scfusa checkwith no corresponding commit here to explain why). Matches the same pinning fix being applied ecosystem-wide for every x-FuSa tool reference across go/cpp/rust x-Net repos + RELAY.Also closed #69 separately — already fixed on
main(CYBERSECURITY.md's SHA-256 claim was corrected in an earlier commit, just never closed).Verification
Built c-FuSa fresh from the pinned
v0.5.46tag and rancfusa check .against this branch: 0 errors (was 20: 10× HARA002, 10× HARA003).Test plan
.fusa-hara.jsonis valid JSONcfusa checkpasses locally against the pinned c-FuSa version