…tant messages (#13744)

## background

when an assistant message contains only tool-call parts (no text),
`convertToOpenAICompatibleChatMessages` and
`convertToOpenAIChatMessages` send `content: ""`. providers backed by
AWS Bedrock reject this with `ValidationException: messages: text
content blocks must be non-empty`

## summary

- change `content: text` to `content: text || null` for assistant
messages in both `@ai-sdk/openai-compatible` and `@ai-sdk/openai`
- update tests to expect `null` instead of `""` for tool-only assistant
messages

## checklist

- [x] tests have been added / updated (for bug fixes / features)
- [ ] documentation has been added / updated (for bug fixes / features)
- [x] a _patch_ changeset for relevant packages has been added (run
`pnpm changeset` in root)
- [x] i have reviewed this pull request (self-review)

## Future work

The same `content: text` pattern exists in `@ai-sdk/xai`,
`@ai-sdk/deepseek`, `@ai-sdk/groq`, and `@ai-sdk/mistral` and will hit
the same Bedrock error under equivalent routing. Tracked separately in
#14612.

## related issues

fixes #13466

## Background

CI was breaking ( a test wasn't updated for some reason ) after this PR
#13744

## Summary

updated snapshot

…sistant messages

When an assistant message contains only tool-call parts (no text),
the converters send content: "". Providers backed by AWS Bedrock
reject this with: ValidationException: messages: text content blocks
must be non-empty.

This applies the same fix from vercel#13744 (openai, openai-compatible)
to the remaining four providers: xai, deepseek, groq, and mistral.

Change: content: text → content: text || null

Fixes vercel#14612

…only assistant messages (#14613)

This is an automated backport of #13744 to the release-v6.0 branch. FYI
@dancer

---------

Co-authored-by: josh <144584931+dancer@users.noreply.github.com>
Co-authored-by: Gregor Martynus <39992+gr2m@users.noreply.github.com>

…or assistant messages with tool calls (#14951)

## background

backport of #14950 from main to release-v6.0

## related issues

backport of #14950
follow-up to #13744

…messages with tool calls (#14950)

## background

#13744 changed `content: text` to `content: text || null` for assistant
messages. this correctly fixed tool-only messages (openai requires
`content: null` when `tool_calls` is present), but also broke the case
where an assistant message has empty text and no tool calls - openai
rejects `content: null` when `tool_calls` is absent with "Invalid value
for 'content': expected a string, got null"

per the [openai api
spec](https://developers.openai.com/api/reference/go/resources/chat/subresources/completions),
content is "required unless `tool_calls` or `function_call` is
specified"

## summary

- only send `null` when `toolCalls.length > 0`, otherwise preserve the
text string
- add regression tests for both `@ai-sdk/openai` and
`@ai-sdk/openai-compatible`

## verification

verified against live openai chat completions api with
`openai.chat('gpt-4o-mini')` - empty assistant content now sends
`content: ""` and returns a valid response

## related issues

follow-up to #13744

…sistant messages

Follow-up to vercel#13744 / PR vercel#13744 which fixed the same pattern in
@ai-sdk/openai and @ai-sdk/openai-compatible.

When an assistant message contains only tool-call parts (no text), these
four providers were sending content: "" — an empty string. Providers
backed by Amazon Bedrock reject this with:
  ValidationException: messages: text content blocks must be non-empty

Change: content: toolCalls.length > 0 ? text || null : text

This matches the OpenAI spec (content is nullable when tool_calls is
present) and what the official OpenAI SDKs send. Updated tests for all
four packages to expect null instead of "" for tool-only assistant turns.

Fixes vercel#14612

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…sistant messages

Follow-up to vercel#13744 / PR vercel#13744 which fixed the same pattern in
@ai-sdk/openai and @ai-sdk/openai-compatible.

When an assistant message contains only tool-call parts (no text), these
four providers were sending content: "" — an empty string. Providers
backed by Amazon Bedrock reject this with:
  ValidationException: messages: text content blocks must be non-empty

Change: content: toolCalls.length > 0 ? text || null : text

This matches the OpenAI spec (content is nullable when tool_calls is
present) and what the official OpenAI SDKs send. Updated tests for all
four packages to expect null instead of "" for tool-only assistant turns.

Fixes vercel#14612

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

…tant messages (#13744)

## background

when an assistant message contains only tool-call parts (no text),
`convertToOpenAICompatibleChatMessages` and
`convertToOpenAIChatMessages` send `content: ""`. providers backed by
AWS Bedrock reject this with `ValidationException: messages: text
content blocks must be non-empty`

## summary

- change `content: text` to `content: text || null` for assistant
messages in both `@ai-sdk/openai-compatible` and `@ai-sdk/openai`
- update tests to expect `null` instead of `""` for tool-only assistant
messages

## checklist

- [x] tests have been added / updated (for bug fixes / features)
- [ ] documentation has been added / updated (for bug fixes / features)
- [x] a _patch_ changeset for relevant packages has been added (run
`pnpm changeset` in root)
- [x] i have reviewed this pull request (self-review)

## Future work

The same `content: text` pattern exists in `@ai-sdk/xai`,
`@ai-sdk/deepseek`, `@ai-sdk/groq`, and `@ai-sdk/mistral` and will hit
the same Bedrock error under equivalent routing. Tracked separately in
#14612.

## related issues

fixes #13466

## Background

CI was breaking ( a test wasn't updated for some reason ) after this PR
#13744

## Summary

updated snapshot

…messages with tool calls (#14950)

## background

#13744 changed `content: text` to `content: text || null` for assistant
messages. this correctly fixed tool-only messages (openai requires
`content: null` when `tool_calls` is present), but also broke the case
where an assistant message has empty text and no tool calls - openai
rejects `content: null` when `tool_calls` is absent with "Invalid value
for 'content': expected a string, got null"

per the [openai api
spec](https://developers.openai.com/api/reference/go/resources/chat/subresources/completions),
content is "required unless `tool_calls` or `function_call` is
specified"

## summary

- only send `null` when `toolCalls.length > 0`, otherwise preserve the
text string
- add regression tests for both `@ai-sdk/openai` and
`@ai-sdk/openai-compatible`

## verification

verified against live openai chat completions api with
`openai.chat('gpt-4o-mini')` - empty assistant content now sends
`content: ""` and returns a valid response

## related issues

follow-up to #13744