Repository navigation
Releases
v2.12.16
What's Changed
- fix: v2.12.16 stop sealing a live operator job as interrupted by @seanbabalala in #155
Full Changelog: v2.12.15...v2.12.16
v2.12.14
What's Changed
- fix: v2.12.14 pinned release download resilience by @seanbabalala in #153
Full Changelog: v2.12.13...v2.12.14
v2.12.11
What's Changed
- fix(release): allow 60 minutes for release verification (v2.12.11) by @seanbabalala in #150
Full Changelog: v2.12.10...v2.12.11
v2.12.9
What's Changed
- feat: purge settled pricing evidence after a retention period (v2.12.9) by @seanbabalala in #148
Full Changelog: v2.12.8...v2.12.9
v2.12.8
What's Changed
- fix: read pricing audit markers and snapshots by key (v2.12.8) by @seanbabalala in #147
Full Changelog: v2.12.7...v2.12.8
v2.12.7
What's Changed
- fix: index pricing recovery attempt lookups (v2.12.7) by @seanbabalala in #145
- test: give Postgres pricing-index fixtures explicit timeouts (v2.12.7) by @seanbabalala in #146
Full Changelog: v2.12.6...v2.12.7
SiftGate v2.12.6 · Gemini 推理强度兼容
修复:Gemini 推理强度兼容
部分兼容代理会把 reasoning_effort 转成旧版 thinking budget,导致 Gemini 3/4 等 level 模型返回 400。v2.12.6 增加按上游和模型选择的推理参数转换,同时保留原有未知代理行为。
私有代理如何启用
在对应 Gemini 节点已有的 request_compatibility 中增加以下字段,不要覆盖其他配置:
request_compatibility:
chat_reasoning_format: google-thinking-levelpi/OpenRouter 的 reasoning.effort 和普通 Chat 的 reasoning_effort 都会转成 extra_body.google.thinking_config.thinking_level。该模式同样适用于 Google 官方 Chat 接口,未来切换上游无需修改客户端。
兼容边界
- 默认
auto仅识别官方 Google / OpenRouter 主机;未知代理继续使用原有 OpenAI effort 行为,不按模型名猜代理能力。 - 可显式选择
openai、openrouter、google-thinking-level、google-thinking-budget。模式作用于整个节点;不同上游方言请拆分节点。 - 原生 Gemini 请求按已知模型区分 level 与旧 budget;现有旧 Gemini/Anthropic 预算映射保持不变。
- 客户端参数优先于另一种格式的节点默认值;矛盾请求明确报错,不能通过丢参数伪装成功。
- OpenRouter 的预算、启停、输出可见性及 Google 嵌套配置得到保留;显式数字预算由上游验证,不虚构精确的数字到 level 映射。
- 嵌套 Google 推理配置进入元数据统计,不新增隐藏推理、请求内容或密钥日志。
- v2.12.5 的 JSON/SSE/历史工具签名透传保持不变;本版不宣称补齐原生 Gemini 工具签名闭环。
验证与升级
- 回归覆盖 JSON/SSE、官方主机、私有代理、别名、默认参数、错误分类、并行晚到签名及两轮工具调用。
- CI 使用独立安装、未修改的 pi 0.73.1 / 1.3.0;包含缺少代理适配时的 400 负向对照。
- 候选代码已使用真实上游验证两版 pi 的 low/medium/high、JSON 请求,以及 high 强度下的两轮工具签名原样回传。
- 安装/升级验收包含 v2.12.5 前序版本。无数据库迁移、权限变更或自动重启;更新运行镜像需要维护窗口。
正式可用以本版本的签名产物校验和 amd64/arm64 冷安装工作流成功为准。请使用已验证的发布清单及不可变镜像摘要。
SiftGate v2.12.5 · pi 与 OpenRouter 签名兼容
Fixed
- Bridge Gemini tool signatures between Google
extra_content.google.thought_signatureand OpenRouterreasoning_detailsin 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|bothfor 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.mdin 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.
SiftGate v2.12.4 · Gemini 工具调用签名透传
Fixed
- Preserve Gemini function-call
thought_signaturevalues across Chat Completions JSON, SSE, and next-turn assistant history. Read both upstream aliases and emitextra_content.google.thought_signaturewithout decoding, trimming, concatenating or fabricating state. - Correlate parallel streaming tool calls by index/ID, including signature-only chunks, late IDs and late signatures after finish/usage frames. Drain through DONE/EOF without losing accounting.
- Keep unsigned tool calls unchanged. Add two-turn HTTP regressions, opaque-string tests and a bounded app/schema fixture setup budget without changing stream I/O deadlines.
Upgrade and safety
- Native upgrade, Fleet and recovery acceptance covers published v2.11.7, v2.12.0, v2.12.1 and v2.12.3 installations.
- No application schema or database migration is introduced by this fix. Upgrading an installation still requires its normal explicit maintenance approval and a brief restart; publishing this release does not deploy existing instances.
- Use the signed installer/manifest and immutable image digest. Follow the customer installation runbook for verified backup/recovery and approved maintenance operations; retain a compatible rollback image.
- Clients must retain the signature field when replaying tool calls. Signature translation to Responses/Messages/native Gemini protocols is outside this Chat-to-Chat fix. Ambiguous unaddressed parallel deltas are not guessed.
PR #142. Release availability requires the matching successful publication and cold-install workflow, not this release note alone.
SiftGate v2.12.3 · Gemini 原生工具
Gemini 原生工具与正式发布修复
- Chat Completions 路由保留 Gemini 原生
googleSearch、enterpriseWebSearch、urlContext、codeExecution、googleMaps工具及支持的别名,不再静默变成普通对话。 - JSON 与 SSE 保留上游提供的 grounding / URL 元数据,流式响应仍经过原有事件钩子,保留末尾元数据和 token 用量。
- 原生工具请求绕过响应缓存;不支持的跨协议工具转换会明确拒绝。已废弃的 GoogleSearchRetrieval 由上游明确报错,不做静默降级。
- 修复原生生命周期验收中,后台版本发现写缓存与已审批 Fleet 计划的竞争:仅对新建的测试实例在首次启动前使用现有主机禁用策略。客户默认设置、配置漂移保护、签名和安装验收门禁没有放宽。
版本与升级说明
本版包含 PR #140 的 Gemini 修复和 PR #141 的发布验收修复。v2.12.2 源码标签保留,但其正式发布没有完成;请使用本版正式附件,不要把旧源码标签当作安装包。
没有新增数据库迁移。发布不会自动更新或重启已有网关。客户升级仍需自己的维护审批、备份与兼容性流程。
Operator / Fleet 计划绑定整个配置目录(包括版本发现缓存):请在生成计划前关闭后台发现并等待保存完成,维护完成后再恢复。计划之后发生配置变化时应重新规划,不要绕过校验。
已知限制
SSE 只能转发上游实际提供的元数据。部分 Gemini 上游流式响应不提供 grounding / URL 来源;需要完整来源引用时请使用 stream: false。本次没有改变 Doubao 的路由或原生搜索能力。
安装
下载本 Release 的安装包、SHA-256 校验文件、发行清单和 Sigstore 证明四件套;按安装文档验证后使用。镜像提供 linux/amd64 和 linux/arm64,优先使用发行清单中的不可变 digest。