chore: release v0.191.0 - #4024
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (1)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (11)
💤 Files with no reviewable changes (9)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe project version changed from 0.190.0 to 0.191.0. The marketing changelog gained a dated v0.191.0 entry with nine change descriptions. Nine individual changelog entries were deleted. Changesv0.191.0 release
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to The v0.191.0 release metadata is consistent and will appear under October 2026. No actionable merge risk remains beyond normal checks. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 3 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![protoreview[bot]](https://avatars.githubusercontent.com/in/4233969?s=60&v=4){kind=small}
There was a problem hiding this comment.
QA panel review — PASS
code-review-structural · head ea1cd02335b5 · formal
Low-risk release PR (v0.191.0): mechanical version bump, changelog consolidation, and marketing data update. The panel raised a single nit — a stale comment in pyproject.toml referencing an old <0.3 cap when the constraint is now <0.4 — and the verifier confirmed it at head. No panel disagreement, no coverage gaps, no prior requests to disposition. Nothing blocks merge.
Findings
| Severity | Location | Finding | Verified | |
|---|---|---|---|---|
| ⚪ | nit | pyproject.toml:76 |
Stale comment references <0.3 cap but constraint is <0.4 |
confirmed · nearby, not gating |
findings JSON (machine-readable)
[
{
"file": "pyproject.toml",
"line": 76,
"severity": "nit",
"category": "maintainability",
"claim": "Stale comment references `<0.3` cap but constraint is `<0.4`",
"evidence": "Line 76 declares the constraint as `langchain-mcp-adapters>=0.2,<0.4`, but the explanatory comment on line 82 says 'past our own <0.3 cap'. This means the comment was written when the upper bound was `<0.3` and not updated when it was relaxed to `<0.4`. A maintainer reading the comment would believe 0.3.x releases are excluded, when in fact they are now allowed.",
"source": "protopatch",
"verdict": "confirmed",
"note": "Verified at head: line 76 is `\"langchain-mcp-adapters>=0.2,<0.4\"` and the comment reads \"past our own <0.3 cap\" \u2014 the comment is stale relative to the actual <0.4 constraint. \u2014 nearby: in code this PR did not change (outside its changed lines and the functions they sit in) \u2014 reported, not gated (#232)",
"nearby": true
}
]1 structural finding(s) are nearby notes, not part of the verdict: they sit in code this PR did not change (outside its changed lines and the functions those lines are in). Worth a look; not a request for this PR.
pyproject.toml:76(nit) — Stale comment references<0.3cap but constraint is<0.4
1 participant
Automated version bump to
v0.191.0. Review + merge through the normal CI/review gate, then push the tag to cut the release:git checkout main && git pull && git tag -a v0.191.0 -m 'Release v0.191.0' && git push origin v0.191.0. The tag push triggers release.yml (Docker tags + GitHub Release + Discord) — don't also workflow_dispatch release.yml afterward (redundant; 422s on the duplicate).Summary by CodeRabbit