docs(release_notes): promote v1.95.0 to stable - #744
Merged
Conversation
Renames the v1.95.0rc1 folder to v1.95.0 and moves the title, slug, date, Docker tag, pip install, and Full Changelog range onto the stable form. The stable cut was tagged on top of rc/1.95.0, so this folds in the two content PRs that landed after rc1: the revert of user-budget enforcement on team keys and the general-login landing fix that sends MCP consent to /ui/connect. The ownership roll-up moves to 294 and the changelog landing page now leads with v1.95.0. The revert gets its own breaking-changes callout, because the v1.94.0 notes carry the opposite one. Reading the two releases in sequence would otherwise leave you with contradictory guidance about whether a personal max_budget applies on a team key. Also clears stale references elsewhere in the docs. users.md still documented skip_user_budget_on_team_key as available, but the flag was deleted along with the enforcement it gated, so leaving it in general_settings is now a no-op. config_settings.md and virtual_keys.md anchored overwrite_user_with_key_hash to v1.95.0-rc.1 rather than the stable version it now ships in.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Promotes
v1.95.0out of release-candidate form, following the same shape as #701 (v1.94.0) and #603 (v1.93.0): rename the rc folder, move the version strings onto the stable form, fold in what landed after rc1, and lead the changelog landing page with it.What moved
release_notes/v1.95.0rc1/becomesrelease_notes/v1.95.0/, with the title, slug (v1-95-0), date, Docker tag (1.95.0), pip install (1.95.0), and Full Changelog range (v1.94.0...v1.95.0) all on the stable form, and the "current release candidate" line dropped.What was folded in
The stable tag was cut on top of
rc/1.95.0, and the range fromv1.95.0-rc.1tov1.95.0is 13 commits. Only two are content:/ui/connectThe rest are backport vehicles (#34811, #35299, #35414, #35552) and a Next.js artifact chore. #34679, #34684, #34685, #34689, and #34691 also appear in that range but were already in the rc1 notes; they landed on main before rc.1 and were separately picked onto the rc branch, so they are not duplicated here. The ownership roll-up moves from 292 to 294, with UI 54 to 55 and Spend / Budgets / Rate Limits 33 to 34.
Why the breaking-changes callout
The v1.94.0 notes carry a
:::dangerblock announcing that user budgets now apply on team keys (#32005). #35271 reverts exactly that, so v1.95.0 gets the mirror-image callout. Without it, anyone reading the two releases in sequence gets contradictory guidance on whether a personalmax_budgetapplies on a team key.Stale references cleared
docs/proxy/users.mdstill describedskip_user_budget_on_team_keyas available in v1.94.0 and above, in two places. The flag was deleted along with the enforcement it gated, so putting it ingeneral_settingsis now a no-op; both passages now say what the behavior actually is and when it changed. I checked this against the source rather than the PR body: the symbol resolves inlitellm/atv1.94.0and is gone atv1.95.0.docs/proxy/config_settings.mdanddocs/proxy/virtual_keys.mdanchoredoverwrite_user_with_key_hashtov1.95.0-rc.1; both now point at the stable version it ships in.I left
docs/a2a.mdalone. It says theagentskey is read correctly "starting in the next release (afterv1.95.0)", which is still accurate; that fix (#35163) ships in 1.96.0.Verification
npm run buildexits 0. The page renders at/release_notes/v1.95.0/v1-95-0with the1.95.0Docker tag, thev1.94.0...v1.95.0compare link, and the breaking-changes block. The old rc path is gone from the build output and nothing in the repo still links tov1-95-0-rc-1.Broken-link output is byte-identical to the pre-change build, 336 entries both before and after, and none is attributable to this page or to the three docs pages touched. The
config_settingsentries that do appear are pre-existing links toenterprise#...and/proxy/pyroscope_profiling.Docker
1.95.0returns 200 from the GHCR manifest API andlitellm==1.95.0is on PyPI, uploaded 2026-08-02 02:51 UTC, which is where the August 1 date comes from.