docs(changelog): cut 0.1.9 - #119
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Fixed entry above documents the /v1 -> /v2 move; the Changed entry kept the pre-move literal, which is not the route this release ships. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. Important Approval pendingCodeRabbit has no unresolved comments, but it could not review the latest commit because the review limit was reached. Follow the review guidance in this comment to continue. 📝 WalkthroughWalkthroughThe changelog now documents release 0.1.9, uses the ChangesRelease documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized changelog-only update with no actionable merge-blocking risk remaining after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🔍 Cursor Review — Consolidated panel
Triggered by @mattmillerai.
Found 1 finding(s).
| Severity | Count |
|---|---|
| 🟢 Low | 1 |
Panel: 6/6 reviewers contributed findings.
…a fix Cutting the `## [0.1.9]` heading turned two intra-cycle bullets into release history that contradicted itself: the Fixed entry said the run path still pointed at `/v1` so every `models.run` returned a bare 404, while the Changed entry said the route was `/v2`. An operator allowlisting the route got two answers. Neither state was ever published — `client.models.run` is new in 0.1.9 (#73), moved to Router in #103, and reached `/v2` in #117, all after the v0.1.8 tag — so the `/v1` 404 fixed nothing a user could have hit. Drop that Fixed bullet and fold its surviving fact (the vendored spec pin and the `check_drift.py` gate) into the Changed entry, which now states the one live route, names the pre-release shapes as pre-release, and no longer bills itself as a wire break against a version that never spoke the old shape. Migration guidance is kept for anyone who tracked `main`. Documentation only; no code or behaviour changes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 participant
Retitles the
[Unreleased]section to[0.1.9] - 2026-09-01ahead of the v0.1.9 release tag (versioning itself is tag-driven; this is the changelog bookkeeping only).🤖 Generated with Claude Code
Summary by CodeRabbit