chore(release): cut v0.7.0 - #516
Conversation
Move the accumulated Unreleased notes (governed automated-essay-scoring adapters, the criterion facets calibration handoff into the Rust-backed many-facet estimator, and the keyboard-scrollable report export accessibility fix) into the [0.7.0] - 2026-08-04 CHANGELOG section, remove the released fragments, and record the cut in a fresh authoritative fragment. Bump the project version to 0.7.0 in pyproject.toml, both crates, and the Cargo/uv lockfiles. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EutV2EWR41JQztSin3kxSm
|
Warning Review limit reached
Next review available in: 1 second Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (9)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Release cut for v0.7.0, packaging the essay-scoring vertical foundation merged since v0.6.0:
EssayPrompt/EssaySubmission/EssayResponseEvidence/EssayScoringRequestcompiling into the shared scoring contracts, at 100% statement + branch coverage.fit_facetsmany-facet estimator with provenance-mutation rejection and fail-closed identity checks.Mechanics (same flow as prior cuts): Unreleased notes moved into
## [0.7.0] - 2026-08-04; released fragments removed; cut recorded in a fresh authoritative fragment (--checkpasses); version bumped 0.6.0 → 0.7.0 inpyproject.toml, both crates, and the Cargo/uv lockfiles.Verification
Release Tagworkflow withrelease_version=0.7.0.🤖 Generated with Claude Code
https://claude.ai/code/session_01EutV2EWR41JQztSin3kxSm
Generated by Claude Code