docs(release_notes): promote v1.93.0 to stable - #603
Merged
Conversation
Renames the v1.93.0rc1 folder to v1.93.0, drops the release-candidate version strings, and updates the tag, pip install, slug, date, and Full Changelog range to the stable form. Folds in the twelve PRs that landed between rc1 and the stable cut (the rc2 AWS credential forwarding fix, the Anthropic passthrough temperature fix, model_armor attachment handling, /v1/models token limits from the cost map, the Docker runtime image fix, the Python 3.14 enablement set, and the ddtrace/mcp/pillow/httplib2/setuptools dependency maintenance bumps) and bumps the ownership roll-up accordingly. The changelog landing page now leads with v1.93.0
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
yuneng-berri
enabled auto-merge (squash)
July 19, 2026 07:38
`npm run build` failed on release_notes/v1.93.0/index.md:291:41:
Unexpected character `3` (U+0033) before name, expected a character
that can start a name, such as a letter, `$`, or `_`
(micromark-extension-mdx-jsx)
Docusaurus parses these notes as MDX, where a bare `<` opens a JSX tag. The
line wrote the Python constraint unescaped:
Raise the requires-python cap to <3.15 so Python 3.14 ...
so the parser hit `<`, expected a tag name, and found `3`. Column 41 is that
digit exactly.
Wrap it in backticks. It is a version constraint, so inline code is the right
markup and matches how the rest of the file writes version strings; `\<3.15`
and `<3.15` would also build but read worse.
This is the only occurrence in the file -- the other MDX-sensitive spans
(`azure/{us,eu}/gpt-5.4` on line 70, `PATCH /team/{team_id}` on line 170) are
already inside backticks and parse fine.
Verified with the same engine the build uses (@mdx-js/mdx): the pre-fix file
reproduces the exact error above, the post-fix file compiles clean.
yuneng-berri
added a commit
that referenced
this pull request
Jul 19, 2026
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`.
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 the v1.93.0rc1 release notes to the stable v1.93.0 entry, following the v1.92.0 promotion precedent: the folder is renamed, the rc version strings, slug, date, Docker tag, pip install line, and Full Changelog range move to the stable form, and the changelog landing page now leads with v1.93.0
Folds in the fourteen PRs that landed between rc1 and the stable cut: the rc2 AWS credential forwarding fix (#32956), the Anthropic passthrough temperature fix (#33244), model_armor attachment handling (#33554), /v1/models token limits from the cost map (#33721) with its malformed-value follow-up (#33864), the Docker runtime image fixes (#33592, #33853), the Python 3.14 enablement set (#33438, #33801, #33798), and the ddtrace/mcp/pillow/httplib2/setuptools dependency maintenance bumps (#33484, #33803, #33093, #33233). The ownership roll-up is bumped accordingly
This documents the pending v1.93.0 that litellm's
patch-1.93.0rc2branch will build (backport PRs BerriAI/litellm#33847, merged, and BerriAI/litellm#33869, in review). Do not merge until that release actually ships, and this note must be updated if the release is re-cut to a different version or SHA