Skip to content

chore: pin x-FuSa spec version to v1.15.2 #93

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SoundMatt merged 1 commit into from
Jul 29, 2026
Merged

chore: pin x-FuSa spec version to v1.15.2 #93

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ and the project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.

## [Unreleased]

- Bump `CFUSA_SCHEMA_VERSION`/`CFUSA_SPEC_VERSION` to x-FuSa spec v1.15.2 — v1.15.1 and v1.15.2 are both pure documentation clarifications (schemaVersion/specVersion format, §1.6.1 Rule A false-positive example) with no required behavior or wire-format changes.

## v0.5.47 — 2026-07-28

x-FuSa spec v1.15.0 adoption + deep-audit bug-fix sprint (issues #73-80):
Expand Down
14 changes: 12 additions & 2 deletions include/cfusa/version.h
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
#define CFUSA_VERSION_MINOR 5
#define CFUSA_VERSION_PATCH 48
#define CFUSA_VERSION_STRING "0.5.48"
#define CFUSA_SCHEMA_VERSION "1.15.0"
#define CFUSA_SCHEMA_VERSION "1.15.2"
/* Bumped from 1.14.0 to 1.15.0: adopts the x-FuSa master spec's v1.15.0
* attestation-carry-forward MUST (already conformant for fmea/tara/
* safety-case/sas; hara's own JSON output now also passes through its
Expand Down Expand Up @@ -41,6 +41,16 @@
* the moment content changes (§1.6.2 MUST); CFUSA-L004 no longer
* false-positives when a callee's name merely has the caller's name as a
* suffix. */
#define CFUSA_SPEC_VERSION "1.15.0"
#define CFUSA_SPEC_VERSION "1.15.2"
/* CFUSA_SCHEMA_VERSION and CFUSA_SPEC_VERSION bumped 1.15.0 -> 1.15.2
* together (as always): both intervening spec releases are pure
* documentation clarifications with zero required behavior/wire-format
* changes. v1.15.1 blessed MAJOR.MINOR.PATCH (not MAJOR.MINOR) as the
* documented format for schemaVersion/specVersion, matching what c-FuSa
* (and every other tool) already emitted. v1.15.2 added an explicit
* false-positive example to §1.6.1 Rule A's placeholder-text deny-list,
* documenting an already-intended tradeoff (resolved via disposition
* waiver, not per-tool detector narrowing) rather than changing it. No
* c-FuSa code changes required for either bump. */

#endif /* CFUSA_VERSION_H */
Loading