docs(release-notes): backfill v1.83.10 breaking-change entry for client-tag stripping - #104
Merged
yuneng-berri merged 1 commit intoMay 8, 2026
Conversation
…nt-tag stripping Document the default-deny policy for caller-supplied tags introduced in v1.83.10-stable: metadata.tags, litellm_metadata.tags, root-level tags, and x-litellm-tags are stripped unless the calling key or team carries allow_client_tags: true. Includes the warning log signature and the restore-prior-behavior recipe.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ryan-crabbe-berri
approved these changes
May 8, 2026
yuneng-berri
deleted the
yuneng/release-notes-v1.83.10-tags-breaking-change
branch
May 8, 2026 22:39
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
2 participants
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
Backfills a Breaking Changes section in the v1.83.10 release notes for the change that gated caller-supplied tags behind
allow_client_tags: true(PR #25905).The behavior change shipped in v1.83.10-stable but was not called out in the release notes, the All settings page, or any of the tag/cost-tracking pages. Customers relying on client-supplied tags for cost attribution have hit silent breakage on upgrade.
The new entry documents:
metadata.tags,litellm_metadata.tags, roottags,x-litellm-tags), with the proxy's WARNING log signature so operators can grep for itallow_client_tags: trueon the key or team metadata, with curl recipes for both/key/generateand/team/newTest plan
release_notes/v1.83.10/index.mdlocally; confirm new section sits cleanly between Key Highlights and New Models / Updated Models../../docs/proxy/tag_routingand../../docs/proxy/cost_tracking#custom-tags