Skip to content

[Automated] Release notes (agentgateway): 1 fix entry - #1444

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
pr-tracker-draft-agentgateway-4115
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
pr-tracker-draft-agentgateway-4115

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

agentgateway/agentgateway#4115 — fix(llm): drop unsigned thinking blocks when replaying Messages to Bedrock

Docs versions: standalone/main, kubernetes/main

What changes for users: Clients that replay Anthropic Messages history to Bedrock can include an assistant thinking block whose signature is empty. The Bedrock request drops that unsigned block instead of sending invalid reasoning content, so the conversation can continue.

What the docs now say: No content page changed. The proposed LLM fix release note says that Messages replay to Bedrock drops assistant thinking blocks whose signature is empty.

Not verified: No cluster or Bedrock provider was configured in this sandbox, so the replay request is unrun. Internal links are unchecked.

How agentgateway-4115 was drafted, and what was not verified

Plan, and what changed it

  • Planned: Write a release-note-only fix entry for Bedrock Messages replay.
  • Learned: The candidate pages describe Bedrock reasoning replay but do not document unsigned thinking blocks as intended behavior, and neighbors/agentgateway-4211.md covers a separate thinking.display forwarding fix.

Why a documentation change is necessary

The diff changes Bedrock conversion so an assistant thinking block with an empty signature is skipped before the request is sent to Bedrock. The test fixture adds exactly that replay case and the Bedrock snapshot no longer contains a reasoningContent.reasoningText block for it. The existing Messages and Bedrock pages explain signed and encrypted reasoning replay, but they do not tell readers to rely on the rejected unsigned behavior, so the user-facing change belongs in the Fixes release notes.

How to verify this change

  1. Configure a Bedrock LLM provider and route /v1/messages traffic to it.
  2. Send a Messages request whose history includes an assistant thinking block with "signature": "", followed by another user message.
  3. Capture the converted Bedrock request or run the reasoning replay request test. The Bedrock request should omit the unsigned thinking block and should not send reasoningContent.reasoningText for Nothing to add.

What was not verified

The configuration and replay request were not applied to a cluster or Bedrock provider, so every verification command is unrun. Internal links are unchecked because Hugo was not run.

How the pages were chosen (triage report)

Draft a release-note entry: a fix no page documents

agentgateway/agentgateway#4115 — fix(llm): drop unsigned thinking blocks when replaying Messages to Bedrock

Release notes

This pull request also adds its release-note entries:

  • content/docs/kubernetes/main/release-notes/release-notes.md: fix(llm): drop unsigned thinking blocks when replaying Messages to Bedrock (fix, under LLM, in a new 1.8 section)
  • content/docs/standalone/main/release-notes/release-notes.md: fix(llm): drop unsigned thinking blocks when replaying Messages to Bedrock (fix, under LLM, in a new 1.8 section)

Draft branch: pr-tracker-draft-agentgateway-4115

Drafts-Commit: a528f46
Signed-off-by: GitHub Action <action@github.com>
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Deploying agentproxy with  Cloudflare Pages  Cloudflare Pages

Latest commit: 9b5a05c
Status: ✅  Deploy successful!
Preview URL: https://7cd3a47a.agentproxy.pages.dev
Branch Preview URL: https://pr-tracker-draft-agentgatewa-kvjd.agentproxy.pages.dev

View logs

@kristin-kronstain-brown

Copy link
Copy Markdown
Collaborator

Closing because this PR only changed release notes. Its entries are now in the combined release-notes PR, #1482.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants