Repository navigation
Conversation
…ease
`rivet review export --release vX [--since <ref>] [--format json]` emits
{command, commit, release, since, count, artifacts[]} where each artifact
carries id, type, title, status, release, description, tags, fields,
links and provenance. A dirty working tree (any porcelain entry,
untracked included) exits 1 naming every dirty path. `--since <ref>`
loads the project at <ref> via the existing git-archive baseline loader
and reports only added/removed/changed artifacts for vX, with
changed_fields on changed ones.
Shape is pinned by schemas/json/review-export-output.schema.json, a
contract test in json_output_contracts.rs, and documented as the
`review-export` docs topic.
Closes #1227
Implements: REQ-416
Verifies: REQ-416
Refs: REQ-007
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KEjmjZqkpapN4wvGGZwHUo
The traceability ratchet flagged REQ-416 (implemented) as new requirement-coverage debt: no feature or design decision satisfied it. FEAT-141 records the review-export feature and closes the gap. Refs: REQ-416 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KEjmjZqkpapN4wvGGZwHUo
Cherry-picking #1232's two commits (from another session) onto main after v0.42.2 put its CHANGELOG entry inside the released [0.42.2] section and duplicated the [0.42.0] heading; the entry moves to [Unreleased] / Added. The review-export docs topic's example used v0.42.0, which docs check refuses now that the workspace is 0.43.0; it uses v0.43.0, and docs/reference is regenerated. requirements.yaml and cmd/mod.rs conflicts kept both sides: REQ-416 follows REQ-417/418, and cmd/mod.rs declares both review and supplier. Refs: REQ-416 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015HMQUV3u86jN2hmCtXNTc9
v0.43.0 was cut without #1232 (owner decision 2026-11-19: review export waits for v0.44.0). After rebasing onto the tag, the CHANGELOG entry landed inside the released [0.43.0] section; it moves to [Unreleased], and REQ-416 moves from v0.43.0 to v0.44.0. Refs: REQ-416 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015HMQUV3u86jN2hmCtXNTc9
4 tasks done
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: 44660a1 | Previous: 593c0d3 | Ratio |
|---|---|---|---|
store_lookup/10000 |
375077 ns/iter (± 1203) |
303035 ns/iter (± 1320) |
1.24 |
This comment was automatically generated by workflow using github-action-benchmark.
avrabe
added this pull request to the merge queue
Nov 19, 2026
Any commits made after this event will not be merged.
📐 Rivet artifact delta
Graphgraph LR
FEAT_141["FEAT-141"]:::added
REQ_416["REQ-416"]:::added
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
Added
Posted by |
This branch has not been deployed
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.
Closes #1227. Replaces #1232, which another session opened 2026-11-12. This session does not push to another session's branch, so #1232's two commits are carried onto this branch unchanged, plus two follow-up commits:
requirements.yamlandcmd/mod.rskeep both sides. The CHANGELOG entry and therivet docs review-exportexample (v0.42.0->v0.43.0, which docs check requires) are moved or updated.[Unreleased], and REQ-416 is scoped to v0.44.0.The feature itself is unchanged from #1232. Its description has the acceptance criteria and design notes:
rivet review export --release vX [--since <ref>] --format json, a commit-pinned snapshot that refuses a dirty tree, with the--sincedelta, therivet docs review-exporttopic and theschemas/json/review-export-output.schema.jsoncontract.Evidence on this branch
review_exportandjson_output_contracts: 10/10 passed.--all --profile ci2786 passed, 3 skipped; fmt andclippy --all-targets -D warnings(default and--no-default-features) clean; traceability ratchet 0 new.rivet docs check0 violations (the released[0.43.0]section matches the tag) andrivet validatePASS.REQ-416 stays
implemented. Verifying it needs an independent acceptance review, which happens in the v0.44.0 scope.Refs: REQ-416
🤖 Generated with Claude Code
https://claude.ai/code/session_015HMQUV3u86jN2hmCtXNTc9