Repository navigation
chore(release): v0.47.0 - #532
Merged
Merged
Conversation
… nine unstarted requirements to v0.48.0 DEC-RELEASE-V047-SCOPE-001 (accepted). v0.47.0 ships how AADL property values are found and applied: references resolve from their declarer (REF-CONTEXT), inline connection properties reach the instance (CONNECTION-INLINE-PROPS), and every analysis resolves a binding by identity (BINDING-CONSUMERS-001). The refined-subcomponent fix (SUBCOMPONENT-REFINE, #517) and property inheritance (PROPERTY-INHERIT) join if verified before the cut. Guard and robustness fixes also ship. - REQ-AADL-BINDING-CONSUMERS-001 -> verified, its scope reduced to the consumers merged in #500, #503, #505, #506, #507/#518, #509, #511 and #514. Three remain as REQ-AADL-BINDING-CONSUMERS-002 (v0.48.0): ARINC 653 partitions (blocked on #504), move-ranking response time (RTA message text), and per-connection bus bindings in bus_bandwidth. - Nine requirements that were never started move to v0.48.0: render x3, TSN CLI/YANG, SysML2 flows/modes, findings layer, DBC cycle time, claim ledger. - REQ-CI-MUTANTS-IN-DIFF-001 had lost its `release: v0.47.0` on main, for a reason not established; it is restored here. Refs #498, #460, #400 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BnBWxgVEUPdsBTLNKtrA6Z
…rity-order fix it depends on REQ-AADL-PROPERTY-INHERIT-001 is implemented and independently verified (#527), but binding threads makes RTA reachable on models where spar orders Priority backwards (#526). It ships with that fix in v0.47.1. Recorded in DEC-RELEASE-V047-SCOPE-001. Refs #460, #526 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BnBWxgVEUPdsBTLNKtrA6Z
…idence and bump to 0.47.0 The v0.47.0 scope (DEC-RELEASE-V047-SCOPE-001) is now all verified, 8 of 8: REF-CONTEXT, SUBCOMPONENT-REFINE, BINDING-CONSUMERS-001, CONNECTION-INLINE-PROPS, SOM-COUNT-CHECKED, WCTT-PMOO-SKIP-VISIBLE, CLOSING-KEYWORD-CROSSLINE, CI-MUTANTS-IN-DIFF. REQ-CI-MUTANTS-IN-DIFF-001 is promoted on the PR-path run of #517 (run 40572309089): 9 selected over 249 changed lines, 6 caught, 3 unviable, 0 missed. That is the first nonzero selection observed in CI, and it matches the local measurement on the same tree. Version 0.46.0 -> 0.47.0 in Cargo.toml, Cargo.lock (workspace members only, `cargo update -w --offline`) and vscode-spar/package.json; `spar --version` prints `spar 0.47.0`. Refs #460, #496, #498, #400 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BnBWxgVEUPdsBTLNKtrA6Z
Rivet verification gate✅ 20/20 passed
Filter: Failed artifacts(none) Updated automatically by |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
v0.47.0: the property-semantics release
This release is about how AADL property values are found and applied. The scope is set by DEC-RELEASE-V047-SCOPE-001, and all 8 requirements in it are
verified:reference (...)value resolves from the component that declared it, as OSATE does{ … }properties reach its instance--pmoorun that declines at a hop says soNine requirements that were never started move to v0.48.0.
Property inheritance (REQ-AADL-PROPERTY-INHERIT-001, #527) moves to v0.47.1. It ships together with the RTA Priority fixes (#528, #531): inheritance binds threads, which makes RTA reachable on models where spar ordered
Prioritybackwards (#526).Falsification. This release is wrong if any of these happens:
reference (cpu)resolves to a component other than the declarer'scpu;The CLI tests named in each requirement fail on v0.46.0.
After merging: a signed tag
v0.47.0on the merge commit. The release counts only once the Release workflow reaches "Create GitHub Release" and at least 19 assets are listed.🤖 Generated with Claude Code
https://claude.ai/code/session_01BnBWxgVEUPdsBTLNKtrA6Z