docs(release_notes): add v1.90.6 and v1.92.1 release notes - #608
Merged
Conversation
Both stables shipped on 2026-07-19 without notes. v1.90.5, v1.91.4 and the v1.93.0 promotion are already covered (#596, #606, #603); these are the two remaining gaps. v1.90.6 builds on v1.90.5: where that release restored the litellm-proxy-extras source folder to the runtime images, this one makes those assets usable from any account by baking the prisma CLI and engines at /opt/prisma, so fresh-database migrations run offline under non-root uids. v1.92.1 backports both Docker fixes onto the 1.92.x line and adds two provider fixes -- Model Armor reference attachments, and dropping an incompatible temperature in the Anthropic passthrough when adaptive thinking is downgraded for pre-4.6 models. Content derived from the actual commit ranges, anchored on the release SHAs rather than tags (these releases were cut from untagged stable-backport merges): v1.90.6 v1.90.5..5113f5d5 8 commits -> 1 content PR (#33853) v1.92.1 v1.92.0..96baca0a 8 commits -> 4 content PRs (#33592, #33853, #33554, #33244) The remaining commits in each range are the version bump, the uv.lock refresh, and dependency maintenance updates, which follow the house convention of being summarized in prose rather than listed as bullets. Format matches the most recent patch notes (v1.90.5, v1.91.4). Docker tags were probed against GHCR rather than derived: 1.90.6 and 1.92.1 both return 200, and the main-v* form 404s, so the Deploy blocks use the bare form. release_notes/ index.md is intentionally untouched -- the landing page lists only minor releases, and no patch note has ever been added to it. Both files verified to compile with @mdx-js/mdx, the engine whose JSX extension broke the v1.93.0 build on an unescaped `<3.15`.
|
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.
The last two stables from 2026-07-19 without notes. v1.90.5 (#596) and v1.91.4 (#606) merged; v1.93.0 is #603.
Content
Derived from the actual commit ranges, anchored on the release SHAs rather than tags — these were cut from untagged stable-backport merges, so
git rev-list v1.90.6finds nothing.v1.90.5..5113f5d5v1.92.0..96baca0aThe remaining commits in each range are the version bump, the
uv.lockrefresh, and dependency maintenance updates — summarized in prose rather than bulleted, matching the convention in v1.90.5 and v1.91.4.v1.90.6 builds on v1.90.5: that release restored the
litellm-proxy-extrassource folder to the runtime images; this one makes those assets usable from any account by baking the prisma CLI and engines at/opt/prisma, so fresh-database migrations run offline under non-root uids.v1.92.1 backports both Docker fixes onto the 1.92.x line, plus two provider fixes — Model Armor reference attachments, and dropping an incompatible
temperaturein the Anthropic passthrough when adaptive thinking is downgraded for pre-4.6 models.Verification
@mdx-js/mdx— the engine whose JSX extension broke the v1.93.0 build on an unescaped<3.15. Also scanned for bare</{outside backticks: none.1.90.6→ 200,1.92.1→ 200,main-v*→ 404. Deploy blocks use the bare form accordingly.litellm==1.90.6and==1.92.1both resolve.v1.90.5andv1.92.0notes both exist onmain.release_notes/index.mdintentionally untouched — the landing page lists only minor releases; no patch note has ever been added to it (v1.90.4, v1.90.5, v1.91.1, v1.91.3, v1.91.4 are all absent), and docs(release_notes): add v1.91.4 release notes #606 didn't touch it either.Known issue, not introduced here
The
## Full Changelogcompare links (v1.90.5...v1.90.6,v1.92.0...v1.92.1) will 404 until those tags are cut — v1.90.6, v1.92.1 and v1.91.4 have no git tag in BerriAI/litellm. I kept the tag-based form to match house convention and because the links resolve once tags exist; #606 has the same property. Flagging so it's a deliberate choice rather than a surprise.