chore: v0.47.0 — declare x-FuSa spec v1.15.2 conformance - #85
Merged
Conversation
Both intervening spec releases (1.15.0 -> 1.15.1 -> 1.15.2) are pure documentation clarifications per §14 of the spec changelog, with no wire-format or required-behavior change: - v1.15.1 blessed the already-in-use MAJOR.MINOR.PATCH form as the correct schemaVersion/specVersion value (a tool emits its SpecVersion constant verbatim; compatibility is still judged on the MAJOR.MINOR prefix only). - v1.15.2 added an explicit worked example to §1.6.1 Rule A with no rule change. While confirming this, found that go-FuSa's own SchemaVersion() helper truncated to a MAJOR.MINOR prefix instead of emitting SpecVersion verbatim, so fmea.json/tara.json/.fusa-hara.json/safety-case.json/ sas.json/sci.json emitted "schemaVersion": "1.15" while every other document (check/trace/qualify/report/gap-reports/sbom/provenance/ audit-pack/capabilities) already emitted the full patch version. Fixed SchemaVersion() to return SpecVersion unmodified, aligning all document kinds on the spec-blessed form. Signed-off-by: Matt Jones <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
SpecVersionfrom1.15.0to1.15.2. Both intervening spec releases are pure documentation clarifications with no wire-format/behavior change (spec §14 changelog): v1.15.1 blessed the already-in-useMAJOR.MINOR.PATCHform as the correctschemaVersion/specVersionvalue; v1.15.2 added a worked example to §1.6.1 Rule A with no rule change.SchemaVersion(), which truncated to aMAJOR.MINORprefix instead of emittingSpecVersionverbatim —fmea.json/tara.json/.fusa-hara.json/safety-case.json/sas.json/sci.jsonwere emitting"schemaVersion": "1.15"while every other document already emitted the full patch version. Now all document kinds emit the same spec-blessedMAJOR.MINOR.PATCHform.Versionto0.47.0and syncs README/tool-safety-manual version references; adds a CHANGELOG entry.Test plan
go build ./...go vet ./...golangci-lint run ./...(0 issues)go test ./... -cover(all packages pass, coverage unchanged from baseline)