chore(release): v0.23.0 — Traceability evidence (REQ-236..242)#646
Merged
Conversation
Six verified requirements make the requirement -> verification -> test chain drift-proof and the validator's signals consistent: - REQ-236 (#556): `rivet check verification-evidence` named-test-exists oracle - REQ-237 (#350): lifecycle gap names the ASPICE verification chain - REQ-239 (#577): validator <-> commit-trailer parser id-shape parity - REQ-240 (#612): configurable release readiness (ready-when + coverage) - REQ-241 (#620): validate and validate --direct produce identical output - REQ-242 (#603): default marker scan reaches workspace member crates Plus the REQ-238 forward-trace mechanism (`rivet trace-results`); the graphical dashboard view is deferred to v0.24 (retagged here). `rivet release status v0.23.0` -> cuttable (6/6 verified). validate PASS, docs check 0 violations. Trace: skip Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
📐 Rivet artifact delta
Graphgraph LR
REQ_238["REQ-238"]:::modified
classDef added fill:#d4edda,stroke:#28a745,color:#155724
classDef removed fill:#f8d7da,stroke:#dc3545,color:#721c24
classDef modified fill:#fff3cd,stroke:#ffc107,color:#856404
classDef overflow fill:#e2e3e5,stroke:#6c757d,color:#495057,stroke-dasharray: 3 3
Modified
Posted by |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
⚠️ Performance Alert ⚠️
Possible performance regression was detected for benchmark 'Rivet Criterion Benchmarks'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.
| Benchmark suite | Current: 0ef17f2 | Previous: 77d5895 | Ratio |
|---|---|---|---|
store_lookup/100 |
2163 ns/iter (± 10) |
1698 ns/iter (± 5) |
1.27 |
store_lookup/1000 |
26350 ns/iter (± 201) |
19248 ns/iter (± 36) |
1.37 |
validate/10000 |
1264762352 ns/iter (± 16023431) |
931701686 ns/iter (± 8664153) |
1.36 |
traceability_matrix/1000 |
61939 ns/iter (± 615) |
41936 ns/iter (± 146) |
1.48 |
query/1000 |
14668 ns/iter (± 155) |
11517 ns/iter (± 43) |
1.27 |
This comment was automatically generated by workflow using github-action-benchmark.
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
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.
v0.23.0 — Traceability evidence
Six verified requirements, each with a regression test proven to fail without the fix.
rivet release status v0.23.0→ cuttable (6/6 verified).rivet check verification-evidence— named-test-exists oraclevalidate⇄--directidentical outputPlus the REQ-238 forward-trace mechanism (
rivet trace-results); the graphical dashboard view is deferred to v0.24 (retagged here, needs Playwright).Version bumped (Cargo.toml/lock + vscode).
rivet validatePASS,rivet docs check0 violations, clippy--all-targetsclean, full suites green — verified locally (org runners busy, draining the queue; the GitHub-hosted release build runs on tag).🤖 Generated with Claude Code