docs: mark LITELLM_JOB_ROLE as unreleased - #1196
Open
Ultronen wants to merge 1 commit into
Open
Conversation
|
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.
Summary
The production guide and configuration reference currently present
LITELLM_JOB_ROLEas an active setting, but LiteLLMmainand released versions do not implement it. The implementation is still under review in LiteLLM PR #36618.This change adds an unreleased-feature warning above the dedicated-worker topology and marks the environment-variable reference as unreleased. It also states that the setting currently has no effect, so operators do not deploy a no-op production configuration.
Addresses BerriAI/litellm#39722.
Verification
npm run lint:writingpassed across 1,016 Markdown files.npm run buildcompleted with exit code 0 and generated the static site. The remaining Docusaurus warnings come from existing, unchanged pages.