fix(bedrock): part-level cache points#14809
Merged
Merged
Conversation
heiwen
changed the title
heiwen
force-pushed
the
fix-bedrock-part-cachepoints
branch
3 times, most recently
from
53ac2a5 to
4b05911
Compare
aayush-kapoor
added
the
backport
Collaborator
|
please fix the merge conflicts and i'll get this merged |
heiwen
force-pushed
the
fix-bedrock-part-cachepoints
branch
from
4b05911 to
b053241
Compare
Contributor
Author
|
Merge conflicts solved. |
aayush-kapoor
approved these changes
May 1, 2026
Contributor
Author
|
Thanks for approving. Anything else needed before it can be merged? |
Collaborator
|
nope should be good |
Contributor
Author
|
Any chance to get this merged soon :) |
github-actions
Bot
removed
the
backport
Contributor
|
|
aayush-kapoor
added a commit
that referenced
this pull request
May 7, 2026
This is an automated backport of #14809 to the release-v6.0 branch. FYI @heiwen This backport has conflicts that need to be resolved manually. ### `git cherry-pick` output ``` Auto-merging packages/amazon-bedrock/src/convert-to-bedrock-chat-messages.test.ts CONFLICT (content): Merge conflict in packages/amazon-bedrock/src/convert-to-bedrock-chat-messages.test.ts Auto-merging packages/amazon-bedrock/src/convert-to-bedrock-chat-messages.ts CONFLICT (content): Merge conflict in packages/amazon-bedrock/src/convert-to-bedrock-chat-messages.ts error: could not apply 9c78e5d... fix(bedrock): part-level cache points (#14809) hint: After resolving the conflicts, mark them with hint: "git add/rm <pathspec>", then run hint: "git cherry-pick --continue". hint: You can instead skip this commit with "git cherry-pick --skip". hint: To abort and get back to the state before "git cherry-pick", hint: run "git cherry-pick --abort". hint: Disable this message with "git config set advice.mergeConflict false" ``` --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Aayush Kapoor <aayushkapoor34@gmail.com>
Contributor
|
🚀 Published in:
|
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.
Background
Bedrock Converse supports prompt cache checkpoints inside
messages[].content[], but@ai-sdk/amazon-bedrockonly preservedproviderOptions.bedrock.cachePointfrom message-level provider options.This meant cache points attached to individual user or assistant content parts were dropped during conversion to Bedrock messages. Requests still succeeded, but Bedrock did not create or read prompt cache entries.
Summary
This PR preserves part-level Bedrock cache points when converting AI SDK messages to Bedrock Converse messages.
It adds cache points immediately after the content part that specified
providerOptions.bedrock.cachePoint, for both user and assistant message content. Existing message-level cache point behavior is unchanged.Regression tests were added for user and assistant content parts to verify cache point placement.
Manual Verification
Ran the Amazon Bedrock provider checks locally:
pnpm --dir packages/amazon-bedrock type-checkpnpm --dir packages/amazon-bedrock testpnpm checkChecklist
pnpm changesetin the project root)Related Issues
Fixes #14808