feat: add experimental latest-user filtering for Bedrock - #17282
Merged
2 commits merged intoDec 2, 2025
Merged
Conversation
|
@uc4w6c is attempting to deploy a commit to the CLERKIEAI Team on Vercel. A member of the Team first needs to authorize it. |
fzowl
pushed a commit
to fzowl/litellm
that referenced
this pull request
Jun 24, 2026
* feat: add experimental latest-user filtering for Bedrock * doc: add experimental bedrock latest-message flag
This pull request was closed.
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
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.
Title
add experimental latest-user filtering for Bedrock
Relevant issues
Fixes #9882
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🆕 New Feature
📖 Documentation
✅ Test
Changes
Case 1: The blocked content exists in a
systemrole messagePreviously, this scenario resulted in a guardrail block because
systemmessages were also included in the moderation target.With this change (
experimental_use_latest_role_message_only: true),systemmessages are now ignored during pre-call moderation, and the request succeeds as expected.Configuration:
curl result:
Case 2: The blocked content exists in the latest user role message
The configuration used here is the same as in Case 1.
Curl Result: