Octafuse v2.1.1
What's changed
Patch Changes
-
8e1f634Thanks @dyc87112! - ### Proxy- User+model 熔断:敏感内容与普通上游 400 共用
20s → 1m → 3m → 5m → 10m退避(不区分请求体);短路用 code 区分类别(circuit.sensitive_content/circuit.client_error)。替换原独立 sensitive-content 熔断实现。 - Images / Audio:退出普通 400(
client_error)熔断,仅保留 sensitive_content 触发。 - Failover:循环内复查已熔断 provider;401/403 provider 冷却由 10min 调整为 5min。
- 错误码契约:网关自造 / 熔断 / 上游分类错误增加固定
code(gateway.*/circuit.*/upstream.*)与响应头X-OctaFuse-Error-Code;body 既有error形状纯增量。 - 诊断:
gateway.upstream_request_failed的 message 附带原始 fetch 错误摘要(与route_resolution_failed一致),便于客户端与 Langfuse 排查。
Admin
- 阿里云模型预设:新增正式版
qwen3.8-max与qwen3.7-flash;同步修正qwen3.8-max-preview的缓存价 / 模态 / 输出上限;qwen3.7-plus/qwen3.7-max的max_tokens对齐为128000。
文档
- 更新 API 与
proxy-request-lifecycle/runtime-data说明,覆盖错误码头与 user+model 熔断行为。
- User+model 熔断:敏感内容与普通上游 400 共用
Container images (GHCR)
Tag v2.1.1 — multi-arch manifest digests (proxy / admin / migrate):
- proxy:
sha256:440f47569ab7556f7d40cd580f1a28357470fdf96f5c206b6ca6ac7265010065ghcr.io/octafuse/octafuse-gateway-proxy@sha256:440f47569ab7556f7d40cd580f1a28357470fdf96f5c206b6ca6ac7265010065
- admin:
sha256:d25587d4695b6f16cf419d29b976fb237d0f0a99a2574926c747d2ae07a01e19ghcr.io/octafuse/octafuse-gateway-admin@sha256:d25587d4695b6f16cf419d29b976fb237d0f0a99a2574926c747d2ae07a01e19
- migrate:
sha256:07fdde839634d4b16f5b6969713d36158d889c998c9a508496bfc9cdd2b7e16cghcr.io/octafuse/octafuse-gateway-migrate@sha256:07fdde839634d4b16f5b6969713d36158d889c998c9a508496bfc9cdd2b7e16c
Pull by digest for reproducible deploys, or by tag v2.1.1 after verifying digest.
Release process: .changeset/README.md · docs/maintainers/release-versioning.md