Revert "docs: add v1.82.3 release notes"

[ghost]

Reverts #23816

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Building	Preview, Comment	Mar 17, 2026 5:26am

[codspeed-hq]

Merging this PR will not alter performance

✅ 16 untouched benchmarks

---

_{Comparing revert-23816-release-notes/v1.82.3 (6d4ffda) with main (d15c2d5)¹}

Footnotes

1. No successful run was found on main (9661249) during the generation of this report, so d15c2d5 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[greptile-apps]

Greptile Summary

This PR reverts PR #23816 ("docs: add v1.82.3 release notes") by deleting the release notes document and partially rolling back changes to provider_endpoints_support.json. The code-level provider implementations introduced in the underlying feature PRs (e.g., sagemaker_nova, nebius messages/responses support) are not reverted — only the documentation artifacts are affected.

Key observations:

• docs/my-website/release_notes/v1.82.3.md is cleanly deleted — this is the stated goal of the revert.
• provider_endpoints_support.json is modified to restore several pre-docs: add v1.82.3 release notes #23816 values: nebius and ZAI capability flags (messages, responses, a2a, interactions) are set back to false/removed, sagemaker_nova is removed, and charity_engine is re-added in its place.
• The deletion of sagemaker_nova from the JSON creates a gap: the provider implementation added by PR feat: add sagemaker_nova provider for Amazon Nova models on SageMaker #21542 remains in the codebase but has no entry in the endpoint support table.
• Nebius and ZAI endpoint support flags (messages: true, responses: true, a2a: true) are reverted to false even though the supporting code is still present.

Confidence Score: 3/5

• Safe to merge for docs rollback, but introduces a lasting inconsistency between provider_endpoints_support.json and the actual codebase state.
• The PR achieves its stated goal of reverting the release notes doc. However, the provider_endpoints_support.json changes are not a pure revert — sagemaker_nova is permanently removed and replaced with charity_engine, while provider implementations added in the original PR remain in the codebase. This means the JSON and the code will be out of sync until a follow-up is made.
• provider_endpoints_support.json — specifically the removal of sagemaker_nova and the capability rollback for nebius and zai.

Important Files Changed

Filename	Overview
docs/my-website/release_notes/v1.82.3.md	Release notes file for v1.82.3 is deleted as part of the revert — straightforward deletion of the docs file added in PR #23816.
provider_endpoints_support.json	Several provider entries are modified: sagemaker_nova is replaced by charity_engine, nebius and zai endpoint support flags are reverted to false, serper URL is updated, and chutes/other providers gain new a2a/interactions fields. The removal of sagemaker_nova may leave the JSON out of sync with the codebase if the provider implementation remains.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR #23816: Add v1.82.3 release notes] -->|Adds| B[docs/my-website/release_notes/v1.82.3.md]
    A -->|Modifies| C[provider_endpoints_support.json\n+ sagemaker_nova\n- charity_engine\n+ nebius/zai capabilities]

    D[PR #23817: Revert #23816] -->|Deletes| B
    D -->|Partially reverts| C

    E[Codebase] -->|Still contains| F[sagemaker_nova provider impl\nPR #21542]
    E -->|Still contains| G[nebius messages/responses support]

    C -->|After revert| H[provider_endpoints_support.json\n- sagemaker_nova missing\n- nebius/zai capabilities = false]

    F -.->|Code-JSON mismatch| H
    G -.->|Code-JSON mismatch| H

Loading

Comments Outside Diff (2)

1. provider_endpoints_support.json, line 2573-2584 (link)

   sagemaker_nova removed, charity_engine substituted

   The sagemaker_nova provider entry is being removed from this JSON and replaced with charity_engine. However, the release notes that are being reverted (PR docs: add v1.82.3 release notes #23816) explicitly describe sagemaker_nova as a new provider implementation added via PR feat: add sagemaker_nova provider for Amazon Nova models on SageMaker #21542. That underlying provider code is not being reverted by this PR — only the docs are. This means the codebase will still contain a sagemaker_nova provider implementation with no corresponding entry in provider_endpoints_support.json, leaving the endpoint support table permanently out of sync with what the code actually supports.

2. provider_endpoints_support.json, line 1486-1510 (link)

   Nebius and ZAI capabilities reverted to false while code may still support them

   messages, responses, and a2a for both nebius and zai are being set back to false (and interactions: true removed). If the underlying implementation changes from PR docs: add v1.82.3 release notes #23816 (and referenced PRs such as feat: add sagemaker_nova provider for Amazon Nova models on SageMaker #21542) are still present in the codebase, this JSON will misrepresent those providers as not supporting these endpoints. The same concern applies to zai at the equivalent block below.

   Consider whether a follow-up PR is needed to re-add the correct capability flags once the docs are ready to go out, or to clearly revert the implementation code as well.

_{Last reviewed commit: 6d4ffda}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6d4ffdad7d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Restore unique provider key for SageMaker Nova

This block reuses the charity_engine key even though providers.charity_engine is already defined earlier in the same JSON object, so JSON parsing keeps only the later value and effectively removes the prior entry while also dropping the sagemaker_nova provider mapping that existed before this revert. That makes provider capability metadata inconsistent with supported providers (for example, sagemaker_nova is still a valid provider in litellm/constants.py) and causes downstream docs/catalog consumers of this JSON to miss SageMaker Nova endpoint support.

Useful? React with 👍 / 👎.