chore: restore stable/1.86.x to 1.86.4 (revert premature 1.86.5 bump)#29644
Conversation
The latest 1.86.x GitHub release is v1.86.3, so the branch should sit one patch ahead at 1.86.4 as the patch-to-be. The GHSA-q775 backport (#29635) additionally bumped 1.86.4 -> 1.86.5, cutting a version ahead of release. This reverts just the version bump and its uv.lock refresh, keeping the backported fix and hardening
Greptile SummaryThis PR reverts the version string in
Confidence Score: 5/5Safe to merge — purely a version string revert with no code or dependency changes. Only two fields change: the version string in pyproject.toml (in both the [project] and [tool.commitizen] sections) and the corresponding entry in uv.lock. No logic, tests, migrations, or dependencies are touched, and the description confirms the security fix and session-token hardening from the backport remain intact. No files require special attention.
|
| Filename | Overview |
|---|---|
| pyproject.toml | Version reverted from 1.86.5 to 1.86.4 in both [project].version and [tool.commitizen].version; no other changes. |
| uv.lock | Lock file updated to reflect the litellm package version revert from 1.86.5 to 1.86.4; no dependency changes. |
Reviews (1): Last reviewed commit: "chore: restore stable/1.86.x to 1.86.4 (..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
What
stable/1.86.x should sit exactly one patch above the latest GitHub release for the line. The latest 1.86.x release is v1.86.3, so the patch-to-be is 1.86.4. The GHSA-q775 backport #29635 additionally bumped 1.86.4 -> 1.86.5, cutting a version ahead of release. This reverts just that version bump and its uv.lock refresh so the line tracks 1.86.4 again; the backported fix (#29612) and the session-token hardening stay in place.
Type
Infrastructure
Changes
pyproject.toml and uv.lock restored to 1.86.4; no code changes