chore: restore stable/1.87.x to 1.87.1 (revert premature 1.87.2 bump)#29645
Open
mateo-berri wants to merge 1 commit into
Open
chore: restore stable/1.87.x to 1.87.1 (revert premature 1.87.2 bump)#29645mateo-berri wants to merge 1 commit into
mateo-berri wants to merge 1 commit into
Conversation
The latest 1.87.x GitHub release is v1.87.0, so the branch should sit one patch ahead at 1.87.1 as the patch-to-be. The GHSA-q775 backport (#29636) additionally bumped 1.87.1 -> 1.87.2, cutting a version ahead of release. This reverts just the version bump and its uv.lock refresh, keeping the backported fix and hardening
Contributor
Greptile SummaryThis PR reverts a premature version bump on the
Confidence Score: 5/5Safe to merge — the change is limited to three version string replacements with no code or dependency modifications. All three version string occurrences are updated consistently, the lock file matches pyproject.toml, and no code, tests, or dependencies are touched. No files require special attention.
|
| Filename | Overview |
|---|---|
| pyproject.toml | Version reverted from 1.87.2 to 1.87.1 in both [project] and [tool.commitizen] sections — straightforward two-line change |
| uv.lock | litellm package version in lock file reverted from 1.87.2 to 1.87.1, consistent with pyproject.toml change |
Reviews (1): Last reviewed commit: "chore: restore stable/1.87.x to 1.87.1 (..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
yuneng-berri
approved these changes
Jun 4, 2026
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
2 participants
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.
What
stable/1.87.x should sit exactly one patch above the latest GitHub release for the line. The latest 1.87.x release is v1.87.0, so the patch-to-be is 1.87.1. The GHSA-q775 backport #29636 additionally bumped 1.87.1 -> 1.87.2, cutting a version ahead of release. This reverts just that version bump and its uv.lock refresh so the line tracks 1.87.1 again; the backported fix (#29612) and the session-token hardening stay in place.
Type
Infrastructure
Changes
pyproject.toml and uv.lock restored to 1.87.1; no code changes