Skip to content

SiftGate v2.12.5 · pi 与 OpenRouter 签名兼容

Choose a tag to compare

@seanbabalala seanbabalala released this 17 Oct 03:14
· 18 commits to main since this release
ffd1632

Fixed

  • Bridge Gemini tool signatures between Google extra_content.google.thought_signature and OpenRouter reasoning_details in Chat Completions JSON, SSE and next-turn assistant history. Opaque signature data is never decoded, trimmed, concatenated or regenerated.
  • Match exact tool-call IDs, not reasoning-detail indexes. Preserve recognized encrypted-detail metadata and sequence. Hold identityless signatures until IDs arrive so early reverse-order signatures do not create placeholder tools in older pi clients.
  • Emit both client dialects while selecting the appropriate upstream dialect: Google by default, OpenRouter for openrouter.ai, with request_compatibility.chat_tool_signatures: google|openrouter|both for private proxies. Removed tool history is not resurrected.
  • Index signature metadata once per message instead of rescanning every parallel call. Text and argument deltas remain streamed immediately.

Verification

  • CI runs real, unmodified pi 0.73.1 and 1.3.0 clients outside the gateway dependency tree, including custom providers, Google/OpenRouter upstreams, parallel tools, early/late/reversed signatures and a missing-bridge negative control.
  • JSON/SSE HTTP contracts and the complete SQLite/PostgreSQL suites remain mandatory before release.
  • Only tool-linked Gemini-compatible encrypted data is bridged. Plaintext reasoning, unrelated IDs, explicit other-provider formats and general cross-protocol reasoning replay are outside this fix. See docs/GEMINI_NATIVE_TOOLS.md in the source tree.

Upgrade and safety

  • Native upgrade, Fleet and recovery acceptance covers v2.11.7, v2.12.0, v2.12.1, v2.12.3 and v2.12.4.
  • This patch introduces no database schema, logging or automatic-deployment change. Use the signed installer/manifest and immutable image digest; follow the customer runbook for verified backup/recovery and approved maintenance. An installation update needs a brief restart and a compatible rollback image.
  • Publishing the release does not update or restart an existing installation. Clients must preserve either supported signature representation when returning tool results.

PR #143. Availability is established by the matching successful signed-publication and cold-install workflow, not a version label alone.