Repository navigation
fix(deps): upgrade DOMPurify to 3.4.17 - #8116
Merged
Merged
Conversation
Upgrade the direct dependency and override to address GHSA-cg2g-xh64-v4q7. Regenerate bun.lock with Bun and update the third-party license inventory.
Contributor
|
Caution Review failedThe pull request is closed. Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
TanTaolov
added a commit
to TanTaolov/new-api
that referenced
this pull request
Oct 30, 2026
1. QuantumNous#7429:个人资料页遵循全局侧边栏可见性 作用:侧边栏模块配置不再绕过后台的全局可见性设置,避免用户误以为配置已生效。 - 侧边栏模块卡片等待侧边栏状态加载完成后再渲染 - 按全局可见性渲染各模块开关与提示状态 2. QuantumNous#7960:先保存 Turnstile 密钥再启用 作用:开启人机验证前强制保存密钥,避免出现已启用但密钥为空的失效配置。 - 启用流程先校验并保存站密钥与密钥 - 补充机器人防护设置组件测试 3. QuantumNous#8006:升级 electron 的 undici 依赖 作用:跟进上游安全与兼容修复,保持桌面端依赖不过期。 - 更新 electron 目录 undici 版本并同步锁文件 4. QuantumNous#8007:升级 fast-uri 到 3.1.9 作用:修复 fast-uri 在 URI 解析上的已知问题。 - 更新 electron 目录 fast-uri 版本与锁文件 5. QuantumNous#8008:升级 electron 到 42.11.16 作用:桌面端跟进 Electron 大版本,获得运行时与安全更新。 - electron 依赖提升至 42.11.16 并同步锁文件 6. QuantumNous#8102:升级 @codemirror/language 到 6.13.1 作用:更新编辑器语言支持,修复语法高亮相关缺陷。 - 更新 web 依赖与 bun 锁文件 7. QuantumNous#8103:升级 marked 到 18.1.2 作用:更新 Markdown 渲染库,修复解析问题。 - 更新 web 依赖与 bun 锁文件 8. QuantumNous#8104:升级 @tanstack/react-query-devtools 作用:调试工具跟进上游版本,减少与 react-query 的版本偏差。 - 更新 web 依赖与 bun 锁文件 9. QuantumNous#8105:升级 knip 到 6.43.0 作用:更新未使用代码检查工具,配合新的检查规则。 - 更新 knip 版本并同步锁文件 10. QuantumNous#8106:升级 tailwind-merge 到 3.7.0 作用:更新类名合并工具,改善 Tailwind 4 下的类合并结果。 - 更新 web 依赖与 bun 锁文件 11. QuantumNous#8112:升级 go-jose/v4 到 4.1.6 作用:跟进 JWT/JWE 依赖的上游修复。 - 更新 go.mod 与 go.sum 中的 go-jose/v4 版本 12. QuantumNous#8116:DOMPurify 升级到 3.4.17 作用:修复 GHSA-cg2g-xh64-v4q7 安全公告涉及的问题。 - 直接依赖与 override 同步提升至 3.4.17 - 重生成 bun 锁文件并更新第三方许可证清单 13. QuantumNous#8117:任务插件按厂商官方路径提供服务并按厂商原样应答 作用:第三方 SDK 或普通 HTTP 客户端可直接把网关当作厂商使用,请求路径、请求体与返回结构保持厂商原生语义。 - 每个插件路由同时挂载在 /{plugin key} 下且只运行该插件,插件可声明厂商官方路径并由网关追加副本,/ali 等旧前缀继续可用 - 多个插件声明同一路径时,提交走所选渠道的插件,查询由任务归属插件应答 - 网关自有路径段(/api、/v1、/v1beta 等)仅内置插件可占顶层路径,插件 key 不得复用这些段 - 即梦改走官方 Bearer API 并移除不可达的 /jimeng 路由,MiniMax 支持 task_id 查询与 /v1/files/retrieve,Vertex AI 兼容 v1beta1 - Vidu 接受 Authorization: Token,Google 接受 x-goog-api-key 与查询参数 key,凭据在日志中脱敏 - 修复 Gemini Veo 从 generatedSamples 取结果、Vertex AI 内联视频回取、xAI 视频查询格式与 predictLongRunning 路由 - 原生请求体不再由插件补全或裁剪字段,DashScope 按客户端调用的端点转发 - 原生应答保留厂商状态码与结构,支持回复包装指定状态与响应头,失败任务不再显示为运行中 - 原生流式请求原样透传厂商事件,事件送达后即结算不再退款,断流按预留量结算并断开下游 - 插件启用、激活或升级版本时与其他插件路径冲突会被拒绝,force 不再跳过校验 - 访问日志统一使用共享查询凭证脱敏,移除 Gemini 的二次脱敏,凭据被剥离后日志只写路径 - 插件页端点去重并支持在厂商路径与 /{key} 地址间切换 14. 任务模型无法计入费用时给出告警 作用:插件缺少定价或无法计费的任务模型会在后台与插件页显式提示,避免静默漏计费。 - 新增模型定价问题聚合与查询接口,插件启用与上传流程返回计费告警 - 前端新增计费问题列表与插件变更提示,模型倍率表与可视化编辑器联动展示 - 补充后端计费问题与前端插件、侧边栏相关测试
3 of 5 tasks
ice-fortress
pushed a commit
to ice-fortress/new-api
that referenced
this pull request
Nov 2, 2026
Upgrade the direct dependency and override to address GHSA-cg2g-xh64-v4q7. Regenerate bun.lock with Bun and update the third-party license inventory. (cherry picked from commit 7743627)
1 of 4 tasks
shirosoralumie648
added a commit
to shirosoralumie648/newapi-rev
that referenced
this pull request
Nov 5, 2026
Sync 75 upstream commit(s) via merge (fork history preserved). Upstream commits: - 7061447 fix(auth): 校验 Redis 鉴权缓存完整性 (QuantumNous#8200) - ba5f736 fix(gemini): bill embeddings from upstream usageMetadata (QuantumNous#8182) - 94b5216 feat(vertex): add per-channel v1beta1 endpoint switch (QuantumNous#8179) - 83b18fe feat(channel): return created IDs with input mappings (QuantumNous#8164) - 52c1730 feat(gemini): add Argon fields and reasoning mappings (QuantumNous#8177) - 9b473a3 fix(twofa): restart the failure count after a lockout expires (QuantumNous#8172) - 45746ee feat(relay): add opt-in HTTP/2 health checks (QuantumNous#8059) - c046559 feat(plugins): bill gemini omni by the tokens vertex reports (QuantumNous#8153) - 651d5a2 fix(xai): preserve token details in stream usage conversion (QuantumNous#6420) - 70e6af6 perf: read and edit request JSON and base64 with moego (QuantumNous#8148) - d0abbf6 feat(plugins): generate video with Gemini Omni on Vertex AI channels (QuantumNous#8142) - ea343c4 fix(plugins): charge relayed streams even when the reserve or task insert fails (QuantumNous#8121) - fe57cba fix(plugins): prefer Kling's returned price (list_price) for Kling 4.0 cash billing (QuantumNous#8125) - 1424ffd fix(plugins): load plugins that declare their own /{key} address (QuantumNous#8119) - 8b253de fix(plugins): keep Kling 4.0 durations in range and map every video size (QuantumNous#8118) - c59f6fd feat(plugins): serve task plugins at the vendors' own paths and answer as the vendors do (QuantumNous#8117) - 37d23dc fix(profile): honor global sidebar visibility (QuantumNous#7429) - 7743627 fix(deps): upgrade DOMPurify to 3.4.17 (QuantumNous#8116) - 883eeb8 feat(plugins): warn about task models a plugin cannot charge - 1e8c707 chore(deps): bump @codemirror/language from 6.12.4 to 6.13.1 in /web (QuantumNous#8102) - 6e78cb3 chore(deps): bump marked from 18.0.6 to 18.1.2 in /web (QuantumNous#8103) - 9fc70bb chore(deps-dev): bump @tanstack/react-query-devtools in /web (QuantumNous#8104) - cef7820 chore(deps-dev): bump knip from 6.27.0 to 6.43.0 in /web (QuantumNous#8105) - 1695171 chore(deps): bump tailwind-merge from 3.6.0 to 3.7.0 in /web (QuantumNous#8106) - 7fa815e chore(deps-dev): bump fast-uri from 3.1.7 to 3.1.9 in /electron (QuantumNous#8007) - ee0f0ac chore(deps-dev): bump electron from 41.10.6 to 42.11.16 in /electron (QuantumNous#8008) - 837b814 chore(deps): bump undici in /electron (QuantumNous#8006) - 3150dfe chore(deps): bump github.com/go-jose/go-jose/v4 from 4.1.4 to 4.1.6 (QuantumNous#8112) - a3851c2 fix: save Turnstile keys before enabling (QuantumNous#7960) - 4193734 fix(logger): keep gin access and recovery logs on the current log file after rotation (QuantumNous#8098) - f366017 Merge commit from fork - 829f082 fix: unmount authenticated layout on sign-out to stop credential-less refetches (QuantumNous#8110) - 9eda50a Merge commit from fork - a2defd2 Merge commit from fork - e449cc7 feat: sample immediate task successes in model performance metrics (QuantumNous#8067) - fcc241c fix: start affinity fallback at the highest channel priority (QuantumNous#8078) - b08ee86 fix(cloudflare): preserve embedding response data (QuantumNous#8041) - 26c488c fix(relay): allow Azure channels to opt in to Responses WebSocket (QuantumNous#8047) (QuantumNous#8075) - 55515db fix(relay): terminate streams on exact bare done markers (QuantumNous#8074) - 49271d2 fix(aws): preserve safeguards in Bedrock Invoke requests (QuantumNous#8071) - 5478811 fix: count completed non-stream relays after context cancellation (QuantumNous#7844) - ad56112 fix(relay): apply GPT-6 chat parameter rules to gpt-6.1-sol and gpt-6.1-terra (QuantumNous#8064) - 01da3a5 perf(relay): stop recompiling param override regexes on every request (QuantumNous#8061) - 34003e9 test: stabilize channel affinity cache keys (QuantumNous#8009) - 0165fef fix(relaykit): preserve Gemini text alongside tool calls (QuantumNous#7998) - 4d962e4 fix(relaykit): preserve tool argument numbers in Claude responses (QuantumNous#7996) - f1569d1 fix(pricing): classify dynamic per-request billing correctly (QuantumNous#8010) - bc795cc fix:修复stop为非字符串和[]string的协议转换问题 (QuantumNous#7935) - 9823ebc fix(billing): bill cache_creation_input_tokens reported in prompt_tokens_details (QuantumNous#7909) - e835b1b chore(deps): bump axios from 1.18.1 to 1.20.0 in /web (QuantumNous#7835) - 5c8032d chore(deps): bump react-i18next from 17.0.10 to 17.1.0 in /web (QuantumNous#7981) - 0b667ca chore(deps): bump i18next from 26.3.6 to 26.5.3 in /web (QuantumNous#7979) - 4105bd0 chore(deps): bump input-otp from 1.4.2 to 1.5.0 in /web (QuantumNous#7980) - b6b85ca chore(deps): bump react-resizable-panels from 4.12.2 to 4.14.6 in /web (QuantumNous#7982) - 1dafb19 fix(gemini): preserve top-level imageConfig in chat conversion - 0034b24 fix(task): wait up to 72 hours before timing out tasks - a404460 chore(web): upgrade Bun to 1.4.4 and use bun check - 33c61a2 fix: prevent stale values when switching edit drawer records (QuantumNous#7989) - 30748c6 fix(logging): 隐藏访问日志中的查询凭据 (QuantumNous#7972) - 7fb6e57 fix(channels): preserve advanced custom body passthrough settings (QuantumNous#7971) - e9d4d63 feat(billing): bill OpenAI 12-hour prompt cache writes at their own price (QuantumNous#7965) - d0b840e fix(relay): keep the client's JSON Schema property order - d8e6561 feat(web): copy model names from usage log details - 8802113 feat(task): let ordinary channels compete on shared plugin endpoints - eb169e7 feat(pricing): adjust synced upstream prices by the site exchange rate - e2321a5 chore(web): sort locale keys - db80ac8 fix(task): let task plugins validate their own requests - dbe97be feat(task): pass client request headers to task plugin drivers - 556517f feat(task): accept multipart bodies on native plugin routes - 94cc3ff fix(billing): bill Claude cache writes that arrive without a 5m/1h split - 7e65967 fix(relay): stop cutting off slow clients during large stream events - 0c2af97 fix(relay): finish delivered Responses streams without false disconnect errors (QuantumNous#7956) - 7d8b912 fix: upgrade Go to 1.26.10 for CVE-2026-111943 (QuantumNous#7942) - 4d36f2c chore(deps-dev): bump vitest from 4.1.10 to 5.0.4 in /web (QuantumNous#7838) - eea05e0 chore(deps): bump github.com/klauspost/compress from 1.18.3 to 1.18.7 (QuantumNous#7931) Local tests not run (CI-only).
10 tasks done
therealemery
added a commit
to therealemery/new-api
that referenced
this pull request
Nov 16, 2026
* Merge commit from fork MaskSensitiveInfo trimmed trailing punctuation one byte at a time and recounted the parentheses of the whole URL for each trailing ')'. Trim the punctuation set, including ')', with strings.TrimRight; the trimmed characters are still appended after the masked URL. * Merge commit from fork Upgrade @visactor/vchart and @visactor/react-vchart to 2.1.7. Since 2.1.6 the DOM tooltip renders the title as text (VisActor/VChart#4640). * fix: unmount authenticated layout on sign-out to stop credential-less refetches (QuantumNous#8110) * Merge commit from fork Cap zstd windows at 8 MiB and the request body limit. Disable asynchronous decoding to avoid consuming bodies before downstream middleware accepts the request. Port the complete zstd fix and regression tests from the related advisory PR without importing unrelated commits. Validation in this repository with Go 1.26.10: GOMAXPROCS=2 go test -p 2 ./middleware -count=1 -timeout=180s GOMAXPROCS=1 go test -p 1 ./middleware -run '^TestDecompressRequestZstd' -count=1 -timeout=60s -v go mod verify All passed, including 14 decoding cases and early rejection without reading the body. * fix(logger): keep gin access and recovery logs on the current log file after rotation (QuantumNous#8098) The gin access logger and panic recovery captured gin.DefaultWriter and gin.DefaultErrorWriter when the server was built. Since log rotation closes the previous file, every [GIN] access line and [Recovery] stack after the first rotation reached stdout/stderr only and never any log file. Both middlewares now write through common.LogWriter / common.ErrorLogWriter, which forward each write to the current gin writers under LogWriterMu, so rotation can swap and close files without losing lines or leaking the old fd. The server-wide recovery moves from main.go to middleware.PanicRecover so the production wiring is covered by the regression test. * fix: save Turnstile keys before enabling (QuantumNous#7960) * chore(deps): bump github.com/go-jose/go-jose/v4 from 4.1.4 to 4.1.6 (QuantumNous#8112) Bumps [github.com/go-jose/go-jose/v4](https://github.com/go-jose/go-jose) from 4.1.4 to 4.1.6. - [Release notes](https://github.com/go-jose/go-jose/releases) - [Commits](go-jose/go-jose@v4.1.4...v4.1.6) --- updated-dependencies: - dependency-name: github.com/go-jose/go-jose/v4 dependency-version: 4.1.6 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump undici in /electron (QuantumNous#8006) Bumps and [undici](https://github.com/nodejs/undici). These dependencies needed to be updated together. Updates `undici` from 7.30.0 to 7.30.1 - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.30.0...v7.30.1) Updates `undici` from 6.29.0 to 6.29.1 - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.30.0...v7.30.1) --- updated-dependencies: - dependency-name: undici dependency-version: 7.30.1 dependency-type: indirect - dependency-name: undici dependency-version: 6.29.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps-dev): bump electron from 41.10.6 to 42.11.16 in /electron (QuantumNous#8008) Bumps [electron](https://github.com/electron/electron) from 41.10.6 to 42.11.16. - [Release notes](https://github.com/electron/electron/releases) - [Commits](electron/electron@v41.10.6...v42.11.16) --- updated-dependencies: - dependency-name: electron dependency-version: 42.11.16 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps-dev): bump fast-uri from 3.1.7 to 3.1.9 in /electron (QuantumNous#8007) Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.7 to 3.1.9. - [Release notes](https://github.com/fastify/fast-uri/releases) - [Commits](fastify/fast-uri@v3.1.7...v3.1.9) --- updated-dependencies: - dependency-name: fast-uri dependency-version: 3.1.9 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump tailwind-merge from 3.6.0 to 3.7.0 in /web (QuantumNous#8106) Bumps [tailwind-merge](https://github.com/dcastil/tailwind-merge/tree/HEAD/packages/tailwind-merge) from 3.6.0 to 3.7.0. - [Release notes](https://github.com/dcastil/tailwind-merge/releases) - [Commits](https://github.com/dcastil/tailwind-merge/commits/tailwind-merge@3.7.0/packages/tailwind-merge) --- updated-dependencies: - dependency-name: tailwind-merge dependency-version: 3.7.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps-dev): bump knip from 6.27.0 to 6.43.0 in /web (QuantumNous#8105) Bumps [knip](https://github.com/webpro-nl/knip/tree/HEAD/packages/knip) from 6.27.0 to 6.43.0. - [Release notes](https://github.com/webpro-nl/knip/releases) - [Commits](https://github.com/webpro-nl/knip/commits/knip@6.43.0/packages/knip) --- updated-dependencies: - dependency-name: knip dependency-version: 6.43.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps-dev): bump @tanstack/react-query-devtools in /web (QuantumNous#8104) Bumps [@tanstack/react-query-devtools](https://github.com/TanStack/query/tree/HEAD/packages/react-query-devtools) from 5.101.2 to 5.105.0. - [Release notes](https://github.com/TanStack/query/releases) - [Changelog](https://github.com/TanStack/query/blob/main/packages/react-query-devtools/CHANGELOG.md) - [Commits](https://github.com/TanStack/query/commits/@tanstack/react-query-devtools@5.105.0/packages/react-query-devtools) --- updated-dependencies: - dependency-name: "@tanstack/react-query-devtools" dependency-version: 5.105.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump marked from 18.0.6 to 18.1.2 in /web (QuantumNous#8103) Bumps [marked](https://github.com/markedjs/marked) from 18.0.6 to 18.1.2. - [Release notes](https://github.com/markedjs/marked/releases) - [Commits](markedjs/marked@v18.0.6...v18.1.2) --- updated-dependencies: - dependency-name: marked dependency-version: 18.1.2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * chore(deps): bump @codemirror/language from 6.12.4 to 6.13.1 in /web (QuantumNous#8102) Bumps [@codemirror/language](https://github.com/codemirror/language) from 6.12.4 to 6.13.1. - [Changelog](https://github.com/codemirror/language/blob/main/CHANGELOG.md) - [Commits](https://github.com/codemirror/language/commits) --- updated-dependencies: - dependency-name: "@codemirror/language" dependency-version: 6.13.1 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * feat(plugins): warn about task models a plugin cannot charge A plugin change can leave a task model without a usable price: no price is set, the price uses usage the plugin no longer provides, or the plugin no longer offers the model. The gateway now lists these models. The list follows the plugins currently serving, so a gateway update that changes a built-in plugin shows up too. - Uploading, installing from the marketplace, activating or enabling a plugin, or deleting its active version, lists the models it cannot charge in the upload dialog or in the notice after the action. - Model pricing marks each of them "Price needs attention" with the reason, and a "Price status" filter lists them. A plugin model that was never priced now appears in the table too. The badge replaces "Task pricing not configured". - The sidebar shows how many models need attention on System Settings, Billing & Payment and Model Pricing, for super administrators. - GET /api/option/model_pricing/issues returns the list. It is root only; access tokens need the option:read scope. - Prices kept for a switched-off plugin are not reported. They apply again when the plugin is switched back on. * fix(deps): upgrade DOMPurify to 3.4.17 (QuantumNous#8116) Upgrade the direct dependency and override to address GHSA-cg2g-xh64-v4q7. Regenerate bun.lock with Bun and update the third-party license inventory. * fix(profile): honor global sidebar visibility (QuantumNous#7429) * fix(profile): honor global sidebar visibility * fix(profile): wait for sidebar status * feat(plugins): serve task plugins at the vendors' own paths and answer as the vendors do (QuantumNous#8117) * feat(plugins): serve task plugins at the vendors' own paths A vendor SDK or plain HTTP client can now point at the gateway and keep the vendor's official paths. Every plugin route is also served under /{plugin key}, and that address always runs that plugin. - Plugins declare the vendor's official paths and the gateway adds the /{key} copy. Existing prefixed addresses keep working, including /ali for Alibaba Bailian. - Several plugins may declare the same path. A submit runs on the plugin whose channel is selected; a query is answered by the plugin that owns the task. - Under the gateway's own path segments (/api, /v1, /v1beta and so on) only built-in plugins get top-level paths; other plugins are served at their /{key} address. Plugin keys cannot reuse these segments. - Jimeng uses the official Bearer API (/api/common/v3/submit_task_v2 and get_result_v2). The /jimeng/ route, which requests could not reach, is removed. - MiniMax supports the official v1 query with ?task_id= and /v1/files/retrieve. The unimplemented GET /v1/files/{id} placeholder is removed. Vertex AI also accepts v1beta1 paths. - Vidu routes accept Authorization: Token, and Google routes accept x-goog-api-key and ?key=. The key is redacted from logs. - Gemini Veo results are read from generatedSamples, so their videos download again. Vertex AI videos returned inline are fetched again when downloaded. - GET /v1/videos/{id} answers tasks created on xAI's routes in xAI's format, and :predictLongRunning requests reach the Veo plugin. - Enabling, activating or promoting a plugin version is refused when it conflicts with another plugin, and force no longer skips that check. - The plugin page lists each endpoint once, with a switch between the vendor path and the /{key} address. Legacy addresses are folded away. * fix(logging): use the shared query credential masking for key= The access log already masks credentials passed in the query string, key included. A second redaction for the Gemini ?key= form rewrote it to key=[REDACTED], so the log showed two masking styles and the masking tests failed. Only the shared masking remains. The Gemini native routes take ?key= out of the URL. With no query left, the log fell back to the path gin recorded on arrival, which still carried the key. The log now writes the path alone in that case, and the plugin API document no longer says the key is logged as key=[REDACTED]. * feat(plugins): answer native plugin routes as the vendors do A request sent to a vendor's own path now reaches the vendor as the client wrote it, and the client gets the vendor's reply shape and status. The gateway answers a native request with its own 400 only when it cannot tell the model, cannot price the request, or cannot provide the feature; the vendor checks everything else. - New gateway rejections of that kind on native routes: callback_url on Ark, Kling, Vidu and MiniMax; Kling external_task_id and a body with model but no model_name; xAI storage_options, which was dropped silently; and for Jimeng, req_json on get_result_v2, a req_key the plugin cannot price, and frames other than 121 or 241. A value the plugin cannot read reserves the model's dearest tier, and settlement is unchanged. - Native bodies are sent as the client wrote them. Plugins no longer fill in MiniMax-H3's duration, resolution and ratio or Vidu's movement_amplitude and images: null, drop Vidu's bgm: false, turn Jimeng's image and images into image_urls, or merge Ark's content. Kling requests no longer carry an added aspect_ratio 1:1, cfg_scale 0.5 or model field; without a size Kling uses its own 16:9. DashScope requests go to the endpoint the client called. - Replies keep each vendor's shapes and error codes. A native presenter may answer with the vendor's own status through a reply wrapper ({__status, __headers, __body}): xAI answers a pending video with 202, DashScope an unknown task with 200 UNKNOWN. A task the gateway failed shows as failed instead of still running. xAI's native query shows a video that failed but was charged as failed with xAI's usage, instead of done; billing is unchanged. - A native client that asks the vendor for a stream (Seedream with stream: true, Wan interleaved output with X-DashScope-Sse: enable) gets the vendor's events as they arrive. Once an event has reached the client the task settles and is never refunded: a finished stream bills what was delivered, and a stream that stopped early bills the reservation and cuts the client's connection, so a downstream gateway keeps its reservation too. The client leaving does not cancel the upstream request, which TASK_PLUGIN_PROTOCOL_TIMEOUT_SECONDS bounds. A JSON reply from an older new-api upstream is still accepted. - Routes that keep no result (retainResult: false) accept replies up to MAX_FILE_DOWNLOAD_MB, so b64_json images fit. - Native decoders get the client's request headers, without gateway credentials, as ctx.requestHeaders. - Native routes accept a channel's model aliases and case variants of model names, as the gateway's own formats do, also on routes that list their models. - Kling lists kling-v2-5-turbo, kling-v2-6 and kling-v3, priced in units per mode, sound and voice; Kling retired kling-v1, kling-v1-6 and kling-v2-master on 2026-09-15. Vidu lists its current models, from viduq4-preview to vidu1.5. - Clients of /v1/videos and the other gateway formats can no longer pass a native body through the field the plugins use for it internally. * feat(plugins): add Kling 4.0 to the kling plugin Kling 4.0 takes the model in the path and has its own request shape, so the plugin serves POST /text-to-video/kling-4.0, /image-to-video/kling-4.0 and /omni-video/kling-4.0 as native routes, and answers GET /tasks?task_ids= for their tasks. /v1/videos and the Responses API send kling-4.0 as text-to-video or image-to-video, with size picking 720p or 1080p. Billing follows Kling's price list: units per output second by resolution, or, with an input video, twice the output, or input plus output when the input is longer. Kling picks the length when the request has none and only Kling knows how long an input video is, so the reservation covers the longest of each. A task settles on the units Kling deducted, or, when Kling took cash, on the durations it reports. Kling 4.0 Flash has no published price yet and is left out. * chore(plugins): bump the task plugins this branch changes Each of these plugins now declares its vendor's own paths and answers native requests as the vendor does; kling also adds Kling 4.0. That is new behavior in every one of them, so each takes a minor version: alibaba 1.5.0, doubao 1.4.0, google 1.2.0, hailuo 1.4.0, jimeng 1.2.0, kling 1.2.0, vertex-ai 1.2.0, vidu 1.2.0 and xai 1.2.0. * fix(plugins): keep Kling 4.0 durations in range and map every video size (QuantumNous#8118) Kling 4.0 makes videos of 3 to 30 seconds. The plugin accepted 1 to 3600, so a longer or shorter duration was reserved and then refunded when Kling refused it. It is now refused before anything is reserved. A /v1/videos size now gets the nearest of Kling's text-to-video aspect ratios, 21:9 included for Kling 4.0, and Kling 4.0 takes 720p or 1080p by the size's shorter side. Before, only four sizes were mapped: 720x720 was reserved at 1080p and 1792x1024 was sent as 1:1. A size that is not WIDTHxHEIGHT is refused. * fix(plugins): load plugins that declare their own /{key} address (QuantumNous#8119) Since the gateway also serves every route under /{key}, a plugin that declared both a top-level route and the same route under its key failed to load with "duplicate route". TypeSafe 1.2.0, already published, declares POST /v1/systemone and POST /typesafe/v1/systemone and stopped loading. The declared address now serves the copy, so the host no longer adds it a second time. * fix(plugins): prefer Kling's returned price (list_price) for Kling 4.0 cash billing (QuantumNous#8125) * fix(plugins): charge relayed streams even when the reserve or task insert fails (QuantumNous#8121) A native route relays the vendor's SSE events to the client as they arrive. If the final reserve or the task insert then failed, the controller refunded the whole reservation. The client kept the images and paid nothing. Once the first event reaches the client, the controller no longer refunds. A failed reserve no longer stops the submission. Settlement charges the actual quota and may overdraw the token, as ordinary settlement does. A failed task insert still settles the charge and writes the consume log. * feat(plugins): generate video with Gemini Omni on Vertex AI channels (QuantumNous#8142) * perf: read and edit request JSON and base64 with moego (QuantumNous#8148) * perf: read and edit request JSON and base64 with moego Switch gjson/sjson to moego/ojson and base64 on media, file and plugin paths to moego/base64. Both keep the same results on valid input. - Param overrides apply every edit to one ojson.Doc and write the body once, instead of copying the whole body for each edit. - The video proxy and the audio check validate base64 without decoding it; plugin icons and inlined plugin files build data URLs directly. - Login, password, OAuth and signature code keeps gjson and encoding/base64. * perf: rewrite request fields without re-encoding the whole body Removing disabled fields, the Responses WebSocket create event, AWS Mantle and pass-through bodies, the OpenAI usage patch, alpha search, video result redaction and image SSE events now edit the body with ojson.Doc instead of decoding it into a map and encoding it again. Everything the gateway does not touch keeps the client's member order, number spelling and characters. - A key the client repeats is removed or rewritten in every copy, so an upstream that reads the last copy sees the same value the gateway routed and billed. A key that appears once is rewritten in place. - Image responses and the video proxy read large values without copying them. * perf: keep member order in param override merges and prune_objects Merging an object (append/prepend) now replaces existing members where they stand and appends new members, sorted by key, at the end. prune_objects deletes the matching objects from the body in place instead of encoding the pruned part, or the whole body, again. Everything else keeps the client's member order, number spelling and characters. * fix(xai): preserve token details in stream usage conversion (QuantumNous#6420) xAIStreamHandler only copied prompt_tokens/total_tokens/completion_tokens when converting the xAI stream usage, dropping prompt_tokens_details (cached_tokens) and completion_tokens_details. As a result cached tokens from streaming grok requests never reach the log, and cache pricing is never applied — cached prompt tokens are billed at the full input rate. Non-stream requests already keep these fields via xAIHandler. Co-authored-by: Claude Fable 5 <noreply@anthropic.com> * feat(plugins): bill gemini omni by the tokens vertex reports (QuantumNous#8153) * feat(relay): add opt-in HTTP/2 health checks (QuantumNous#8059) * fix(twofa): restart the failure count after a lockout expires (QuantumNous#8172) IncrementFailedAttempts kept the stale counter after a lockout window expired, so the first wrong code after expiry computed MaxFailAttempts+1 and re-locked the account for the full LockoutDuration. When the stored lockout has expired, start a new window at 1 and clear locked_until. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> * feat(gemini): add Argon fields and reasoning mappings (QuantumNous#8177) * feat(channel): return created IDs with input mappings (QuantumNous#8164) * feat(channel): return IDs of newly created channels 1. Preserve the success envelope and return created IDs for single and batch requests. 2. Keep generated IDs in the input slice and propagate panics after transaction rollback. 3. Document the response and cover duplicate credentials, chunk boundaries, empty batches, and rollback. * feat(channel): map creation results to original inputs Return input_index and channel_id for each accepted input while preserving existing IDs and credential parsing. Cover filtered empty inputs, duplicate keys, Vertex JSON, and multi-key channels in the API contract tests and OpenAPI examples. * feat(vertex): add per-channel v1beta1 endpoint switch (QuantumNous#8179) * feat(gemini): add Argon fields and reasoning mappings * feat(vertex): add per-channel v1beta1 endpoint switch * fix(gemini): bill embeddings from upstream usageMetadata (QuantumNous#8182) * fix(auth): 校验 Redis 鉴权缓存完整性 (QuantumNous#8200) * fix(auth): verify Redis authentication cache integrity * fix(auth): repair auth cache hashes with unreadable fields A token cache hash with a field that cannot be parsed, or with a stray DeletedAt field, fell back to the database on every request and was never rewritten. Repairs now read the stored signature on its own, drop DeletedAt, and replace quota counters that are not integers in both the token and user caches. Valid counters are still kept. * feat: forward image complexity and markup for gpt-image-2.6 (QuantumNous#8208) * fix(pricing): guide users through model pricing issues * fix(pricing): review model price changes before saving - Count pricing issues only for models an enabled channel serves, under its own name, a case variant or an alias. Stale saved prices still count. - List built-in prices only when they are saved or a channel serves them. - Keep deletions as drafts: a deleted row stays in the table with Undo until saved, and a row without a saved price has no delete action. - Show old and new prices on changed rows and in the editor, and confirm every save with a per-model list of current and new prices. - Count and confirm expression price edits; the form fields now take precedence over the option keys loaded with the page. - On phones, give the tabs their own scrollable row and move secondary actions into a menu. * fix(cache): 修复用户和令牌缓存的 Redis 跨槽错误 (QuantumNous#8218) * fix(cache): colocate user and token auth keys in Redis slots Use shared hash tags for cache hashes and authentication fences. Add regression coverage for matching tags and document coordinated rollout requirements. AI-assisted implementation and tests. * fix(cache): keep cache key names and tag fences with them Renaming user:<id> and token:<hash> split quota counters and invalidations between old and new nodes during a rolling upgrade. Keep those names and tag the fence and version keys with the cache key instead, so each script still touches a single slot. --------- Co-authored-by: CaIon <i@caion.me> * fix: clarify session cache actions and expose per-rule clearing * fix(vertex): cache service-account access tokens until they expire The old cache stored the "not found" result of the first lookup and never accepted the new token afterwards, so every request signed a new JWT and exchanged it with Google. Tokens are now kept per channel key slot until 5 minutes before the expires_in Google returns (one hour when it is missing). Concurrent requests share one exchange, a replaced service-account key gets a new token, and failed exchanges are not cached. * refactor(aws): remove the unused api_key HTTP request path The relay never calls GetRequestURL before DoRequest, so the api_key branch that built a /converse URL was never reached. API keys in the "<api-key>|<region>" form already go through the AWS SDK with a bearer token. Remove the dead branch and add a test for the SDK request. * fix(plugins): serve uploaded plugins at top-level /v1 paths (QuantumNous#8241) Since QuantumNous#8117 only built-in plugins were served at top-level paths whose first segment the host uses (api, v1, v1beta, mj, pg, dashboard), so a plugin installed from the marketplace lost addresses such as TypeSafe's POST /v1/systemone and was only reachable under /{key}. Every plugin is now served at its top-level paths. A path a host route answers first, or one under another plugin's key, is still left to /{key}. * fix(channel): restore a multi-key channel when a key is enabled after all keys failed When request failures disabled every key of a multi-key channel, enabling one key again left the channel auto-disabled. Enabling a key now restores the channel in this case too. A later manual or tag disable is kept. * fix(channel): keep a manual channel disable when a request fails A request that failed after an admin disabled a channel changed it to auto-disabled, so automatic channel tests could enable it again. A failure no longer changes a manually disabled channel. * fix(sqlite): keep the default SQLite settings when SQLITE_PATH is a plain path A SQLITE_PATH without parameters replaced the WAL, busy timeout and BEGIN IMMEDIATE settings, so concurrent writes could fail with "database is locked". A plain path now gets the default parameters; a value with its own parameters is used as given. * feat(deepseek): 补全 Responses 工具历史缺失的 reasoning (QuantumNous#8162) * fix: 补全 DeepSeek Responses 工具历史的 reasoning * fix: 忽略 DeepSeek 官方主机名的大小写 * fix: 在参数覆盖后补全 DeepSeek Responses reasoning * feat(plugins): add gemini omni 1.2 flash and send every input image to vertex (QuantumNous#8228) * feat(plugins): add gemini omni 1.2 flash and send every input image to vertex * fix(plugins): report why a gemini omni interaction failed * chore(plugins): bump vertex-ai plugin to 1.3.0 * feat(channels): 高级自定义渠道增加 DeepSeek 搜索与抓取路径选项 (QuantumNous#8250) * feat(channels): 添加网页搜索和网页抓取的路径选项 * feat(channel): 重命名工具标签为 DeepSeek Search 和 DeepSeek Fetch 新增测试文件,验证路径选项和标签的正确性 --------- Co-authored-by: longtsing <wangqinglong605504@cma.cn> * fix(oauth): persist inviter when creating OAuth users (QuantumNous#8247) * fix(web): translate legal consent text on auth pages (QuantumNous#8254) Wrap the terms footer sentence and link labels in t(), replace the hardcoded ' and the ' in legal consent with t('and'), add the footer keys to all locales, and fix the Vietnamese 'and' translation. * feat: support HOST env to set the listen address (QuantumNous#8269) * fix(deepseek): map developer role to system for chat completions (QuantumNous#8287) DeepSeek Chat Completions rejects the developer role. Rewrite developer messages as system messages before sending them upstream; the Responses API accepts developer and is left unchanged. * feat(payment): 易支付支持 RSA 签名方式 (QuantumNous#8291) * feat(payment): 易支付支持 RSA 签名方式 支付设置新增「签名方式」,可在 MD5 与 RSA 之间二选一。默认 MD5,已配置 MD5 的站点升级后行为不变。 - RSA 模式用商户私钥签名下单请求,跳转 /api/pay/submit;充值和订阅回调用平台公钥验签,MD5 签名的回调会被拒绝 - 保存时校验密钥:RSA 生效期间商户私钥和平台公钥必须能解析,切换到 RSA 前要先保存两把密钥;读取设置时不返回密钥 - 设置页选择 MD5 时只显示商户密钥,选择 RSA 时显示商户私钥和平台公钥;七种语言补齐文案 - go-epay 升级到 v0.0.6 * refactor(payment): 易支付签名设置改用 payment_setting 注册配置 签名方式、商户私钥、平台公钥改为 PaymentSetting 的字段,键名为 payment_setting.epay_sign_type、payment_setting.epay_merchant_private_key、payment_setting.epay_platform_public_key,由配置管理器统一加载和保存,不再在 option.go 里逐项初始化和赋值。 - 保存校验移到 operation_setting.ValidateEpaySignOption,规则不变 - 读取设置时不返回以 private_key 结尾的配置项;平台公钥可以正常显示和修改 * fix(channels): 切换渠道时重置模型重定向同步状态 (QuantumNous#8304) * fix(channels): reset model redirect sync state when switching channels * fix(channels): rebase batch redirect sync on current mappings and add regression tests * fix(web): sync risk confirmation text on composition end and blur * perf: 升级 MoeForge moejs/moego,请求体按需流式读取 (QuantumNous#8311) - moejs 迁到 github.com/MoeForge/moejs v0.1.0,Dockerfile、Electron 构建与发布流程的 PGO 路径同步更新;发布附带 THIRD-PARTY-LICENSES.md,并补充 moejs 附带的第三方声明。 - moego 升级到 v0.1.0-alpha.2:宿主 JSON 编解码经 common/kitutil 封装改用 moego/json,根模块和 relaykit 生产代码的 regexp 改用 moego/regexp。 - 内存中的请求体由校验器零拷贝解析;磁盘缓存的请求体经独立文件读取器解码,且只接受一个 JSON 值,尾随内容会被拒绝。 - 模型/分组提取与重复 model 键检测、渠道亲和 JSON 路径、任务协议 stream/background 标志、multipart 解析在磁盘模式下不再把整份请求体读进内存。图片透传直接转发已存储的请求体,并校验最终发往上游的 n。 - 出站请求体各自持有读取位置。此前透传重试共用存储游标,上一次尝试仍在发送时,下一次尝试可能发出残缺的请求体。收到响应头后不再提前关闭请求体,避免中断仍在发送的请求体。 - 表达式计费只在表达式使用 param() 时冻结请求体,其余情况不再读取并保留整份请求体。 * feat(plugins): add provider plugins, request plugins and a community marketplace (QuantumNous#8271) * feat(plugins): add provider plugins, request plugins and a community marketplace - Provider plugins turn an upstream vendor into a channel type: routes, protocol conversion, models, static keys, sign-in flows with token refresh, balance queries, per-channel config and a scheduled hook. - Request plugins run on requests and replies (ingress, request, outbound, egress, reply, report), with instances by scope, model ranges, dry runs and per-log records. Built-ins: request filter, request redaction, parameter override, auto reasoning effort, image compression and content moderation. Sensitive words move into a request filter instance on first start. - Node sync: a system_sync_topics table lets every node reload settings, channels, plugins and other data within seconds, and the system info page shows each node's state. - Marketplace: a community source next to the official one, lookup by plugin code for official and community plugins, key rules for community plugins, install counts and takedown warnings. * docs(plugins): name request protocols and host-only members in the plugin API - Protocol names: ctx.format and samples use relaykit's protocol names. The spec lists the client paths and body of each name, so every host passes the same names to plugins. - Host-specific members: channel, group, user, token, channelTypes, channelOther and utils.paramOverride exist only on new-api. The types mark them optional. - Relay routes: the spec now writes out the route keys and the converters each incoming path accepts. The schema lists the converter names. * feat(plugins): show recommended plugins from the official list too The site now marks official plugins as recommended in its index. The built-in official and community lists both get a Recommended group; lists added by the administrator still cannot recommend plugins. * feat(plugins): fall back to www.newapi.pro when www.newapi.ai does not answer Plugin lists, plugin files and logos from www.newapi.ai are downloaded from www.newapi.pro, the mainland China site, when newapi.ai gives no answer within 10 seconds; the browser remembers this for a day. The marketplace toolbar has a download site picker: Auto, or Mainland China to always use www.newapi.pro. Saved source addresses stay on newapi.ai, and every file is still checked against its sha256. Community install counts go to newapi.ai first and to newapi.pro when newapi.ai cannot be reached. * fix(plugins): leaving the page does not switch the plugin site to www.newapi.pro Reloading or leaving the marketplace cancels requests still running. That was read as www.newapi.ai not answering, so the browser moved to www.newapi.pro for a day although newapi.ai was reachable. Requests cut off by leaving the page are no longer counted. * feat(plugins): choose the plugin download site by hand The marketplace no longer switches between plugin sites by itself. The toolbar menu lists the main site www.newapi.ai, the backup site www.newapi.pro and the other plugin lists; picking an entry is the only thing that changes where plugins are downloaded from, and the main site can always be picked again. A browser that the earlier automatic switch had moved to www.newapi.pro opens on the main site again. The download site, the source choice and managing sources now share one menu in the list header. * feat(plugins): show plugin usage guides and require README and changelog Every marketplace plugin version now ships a usage guide, README.md, and a changelog, CHANGELOG.md, next to plugin.js. The install dialog shows the guide in the reader's language when a translation is listed, falls back to English, and links to the source file. A guide or changelog that breaks the format is reported with its file, line and rule instead of being shown. The plugin API document describes both formats, the translations they may list, and the checks the community marketplace runs before it accepts a version: readme_missing, readme_invalid, changelog_missing and changelog_invalid. Versions accepted before these checks are not checked again. * fix(plugins): address review findings on plugin parts, limits and access - Only the root user reads request plugin instance configs; an admin who may bind instances to channels gets them without configs. - Outbound hooks that grow the body are held to MAX_REQUEST_BODY_MB, as ingress hooks are, and answer 413 without a retry. - An admin who cannot read plugin options keeps the balance and model list actions on plugin channels; the server answers whether they work. - Reading the parts of a plugin source gives up when the source does not parse or code elsewhere refers to meta, as the meta preview does. * fix(plugins): address review findings on request processing, documents and node sync - PDF checks resolve indirect parameters and bound every value the parser allocates or loops on: predictor columns, object stream counts, nested object streams, cross-reference streams and ToUnicode ranges. Font and CMap work checks the deadline. - A WebP frame must match its declared canvas, and keyword search stops at its match limit. - Request processing treats a body as JSON whenever the gateway parses it as JSON, keeps Gemini reply parts in place, scopes instances by the settled auto group, hides channel header overrides from plugin param overrides, and captures replies only for report instances in scope. - Request processing no longer follows the plugin master switch, which now covers plugin tasks and channels only. - json.patch copies stop at MAX_REQUEST_BODY_MB, and provider prepareRequest effects past it answer 413. - Image billing reads the count from the final upstream body, including the count members of SiliconFlow, Imagen and Replicate and the Imagen default. - Automatic channel status changes no longer reload every node's channel cache. A credential refresh holds no channel lock while it waits on the vendor. A key that needs login is disabled and the request can retry. - Balance requests must go to the channel host or allowedHosts, and provider stream events a plugin drops keep the stream alive. - Node sync: OAuth provider writes bump inside their transaction, a failed startup load is retried, and each node is judged by its own topics. - request-filter checks the text the old sensitive-word check did, request-redact and content-moderation handle large inputs, and image-compress lossless mode leaves JPEG and WebP alone. * fix(plugins): address the second review on balances, egress and routes - Channel other_info writes (status changes, balance queries and manual multi-key actions) only land while other_info is still the value read, and retry otherwise, so a write on one node no longer overwrites another node's balance or status reason. They write only their own columns. - On the Responses path egress reads the body after the channel finalizes it, which is the body sent upstream. - The Vertex AI plugin picks the region by the model the client asked for, as the built-in Vertex AI channel does. - /request-processing and /security are reserved route namespaces, and a test checks that every console page is reserved. - The plugin API docs say what egress reads on a provider plugin channel. * feat(channels): run the balance update as a system task with progress "Update all balances" now queues a channel_balance system task instead of starting a goroutine guarded by an in-process flag. The task row holds the progress (enabled channels queried of total), so any node can answer it, and its active key keeps one run at a time across nodes. The CHANNEL_UPDATE_FREQUENCY schedule becomes the same task's schedule, so manual and scheduled runs no longer overlap. GET /api/channel/update_balance answers with the task id, and with the running one when a run is already queued. GET /api/channel/update_balance/task/:task_id, under the same channel permission, returns the status, progress and failure of balance update tasks only. The channel list follows the task, reloads as more channels are queried and once more at the end, and reports how the run ended. * feat(system): sync nodes through system tasks and clean up task history Node sync no longer needs its own table. A write to synced data adds a pending sync_<topic> system task. Every node polls the newest task of each topic it keeps every 3 s and reloads when that task is newer than the one it applied. Custom OAuth providers still add their task inside the write transaction, and lock the newest task of the topic first, so tasks commit in id order. The master marks a sync task succeeded once every online node that keeps the topic has applied it. Until then the task shows how many nodes have applied it and why the others have not. The system_sync_topics table is gone. A composite (type, id) index answers the newest task of a type from the index. The latest-per-type and earliest-pending queries now read ids first, because MySQL 5.7 scanned the whole table for them. A daily system_task_cleanup task deletes finished system tasks older than system_task_setting.retention_days (default 30, at least 1), in batches. It never deletes active tasks or the newest task of any type. The retention is set under Operations > Log maintenance. * chore(plugins): release vertex-ai 1.3.1 (QuantumNous#8313) The Vertex AI plugin now reads the channel deployment region (QuantumNous#8271), which the published 1.3.0 does not. Give that code its own version so the built-in plugin matches the marketplace again. * chore(web-deps): upgrade frontend dependencies (QuantumNous#6999) Upgrade frontend dependencies, keeping the newer of this branch's targets and main's versions. - Notable upgrades: motion 13, nanoid 6, jsdom 30, @base-ui/react 1.7, lucide-react 1.34, @rsbuild/core 2.2, recharts 3.10.1, shadcn 4.19, react 19.2.8, react-hook-form 7.86, @hookform/resolvers 5.9. - Kept main's pins: dompurify 3.4.17 and katex 0.18.2. - oxlint stays on 1.74: 1.79 splits the React Compiler rule and reports 158 new errors on existing components. - sonner 2.0.8 replays active toasts to a newly mounted Toaster, so the marketplace install dialog test now dismisses toasts between cases. * perf(password): improve password validation and feedback (QuantumNous#6928) Show live password strength feedback that follows the account password policy (8–128 characters). - Sign-up, change password, setup wizard and the admin user drawer show a strength meter, the length requirement and optional tips for a stronger password. Only the length blocks submission. - Strength is rated mainly by length. Common passwords, one repeated character and straight runs such as 12345678 or qwertyui are marked as easy to guess, but only when they make up the whole password. - The confirmation field says whether the passwords match, and a mismatch is shown only once. - Password fields get a labelled show/hide button and link their hints for screen readers. - Removed the unused 20-character limit and its translations. * fix(i18n): name the super admin in the compliance lock notice (QuantumNous#6955) The notification settings restructure from this branch is already on main (QuantumNous#7868). What remains is a wording fix in the payment compliance notice. - zh, zh-TW, ja, ru, vi and fr now say "super administrator" in the notice that locks payment, redemption codes, subscription plans and invitation rewards, matching the rest of the UI. - fr: replaced the stray Chinese word in "codes de兑换" with "codes d’échange". * fix(web): align TanStack router devtools with the router core (QuantumNous#8320) react-router-devtools 1.167.1 ships router-devtools-core 1.168.1, which calls interpolatePath() with one object, but it resolved the top-level router-core 1.171.34, where interpolatePath takes positional arguments. In dev mode the devtools panel threw "path.endsWith is not a function" on every route change. - Bump @tanstack/react-router to ^1.170.41 and @tanstack/react-router-devtools to ^1.167.2. - The router, the devtools and the router plugin now share one router-core, 1.171.34. - Production builds do not include the devtools. * fix(web): keep channel plugin settings inside the drawer (QuantumNous#8323) A fieldset's default min-width is its content width, so a long line in the plugin settings JSON editor widened the fieldset past the grid column and pushed the plugin settings out of the channel drawer. Set min-w-0 so the fieldset shrinks with its column and the editor scrolls long lines itself. * fix: 升级 moego 到 v0.1.0-alpha.3,修复无 AVX 的 x86-64 CPU 上的 SIGILL 崩溃 (QuantumNous#8322) - rc.50 依赖的 moego v0.1.0-alpha.2 只按 AES-NI 选用 hashAES 内核,而该内核是 VEX 编码,需要 AVX。在有 AES-NI、没有 AVX 的 CPU(如 Celeron J4125)上,解析不少于 128 字节的请求 JSON 时进程因 SIGILL 退出,容器反复重启。 - alpha.3 在这类 CPU 上改用 SSE 编码的 AES 指令,结果与其他 CPU 相同。根模块和 relaykit 同步升级,THIRD-PARTY-LICENSES 中的版本号同步更新。 Fixes QuantumNous#8314 * feat: add doubao-seedream-5-5-261028 (QuantumNous#8324) * docs(plugins): recommend a summary length that fits one marketplace line The plugin site's marketplace list shows meta.description on one line and cuts longer summaries off with an ellipsis. Measured on the live list at desktop width, the summary column is 572 px at 14 px: 40 Chinese characters fit and 41 do not, and real summaries of up to 80 columns (CJK and full-width punctuation counting as two) all fit. Add a "Plugin summary length" section to the API reference recommending at most 80 columns per locale, with guidance on what to leave to the usage guide, and point the manifest table and the Meta type at it. * feat(plugins): 请求处理插件可声明作用范围,管理员确认一次即自动覆盖 (QuantumNous#8335) * feat(plugins): let request plugins declare where they run A request processing plugin can declare meta.scope: the models and channel types it is made for. An administrator confirms that scope once ("Where the plugin suggests") and the instance then runs on every matching request, new channels and models included. The instance runs only where both the confirmed scope and the plugin's current scope hold, so an update that narrows the scope applies at once and one that widens it waits until an administrator confirms it again. The save API accepts only the declared scope or the one saved before. Instances placed by hand work as before. * feat(plugins): let several plugins declare one channel type A built-in channel type used to belong to one plugin: a second plugin declaring it was rejected with "channelType N conflicts". Community plugins for the same vendor (several Zhipu plugins, say) could not be enabled together. Now every plugin declaring a channel type is indexed for it. A channel of the type serves each of them: its plugin extensions list their models, and a request runs the plugin whose model it asks for, the first in key order when several share the model. Model names that differ only in case and protocol clashes still conflict. * fix(plugins): match each request plugin scope on its own (QuantumNous#8341) An instance with a plugin scope runs where both the confirmed scope and the scope its plugin declares now hold the request. The two lists were intersected word for word, so a confirmed gpt-4o and a declared gpt-4o@effort:high shared nothing and the instance was skipped for gpt-4o@effort:high, which both hold. Each scope now matches the request on its own, modifiers included, and the instance runs when both match. The docs also say that a task submitted before a scope change still reports to the instances it stored, as for hand-placed instances. * docs(github): slim agent issue and PR templates (QuantumNous#8344) Move the out-of-scope list, filing gates, required facts, and writing rules from the agent templates into .agents/github/CHECKS.md, so the posted body keeps only Agent, Request summary, Summary, Evidence, and Merge Danger or Blast Radius. Replace the verbatim user request with a short summary, collapse the Agent block to one line, and require a diagram in Summary when a PR changes a flow, call chain, state, or layout. * fix(relay): keep request-triggered errors from disabling channels (QuantumNous#8345) Errors new-api raises itself because of the request no longer count against the channel: - A param override condition that meets a request value of another type (for example a string temperature in a numeric gt rule) now returns a 400 invalid_request that is not retried, instead of channel:param_override_invalid, which was retried on every channel and could auto-disable each of them. Invalid rules that fail every request (non-numeric rule value, unsupported mode) stay channel errors. - Image conversion failures use the shared convert-request-failed error, so they are no longer retried on other channels. - Automatic channel disabling skips errors classified as local by the request policy log, so a local status or a disable keyword echoed from client input cannot disable a channel. Upstream responses that adaptors report as new-api errors, and local wrappers around an upstream error, keep their upstream classification. The logged health entry now uses the same decision. --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: RedwindA <128586631+RedwindA@users.noreply.github.com> Co-authored-by: feitianbubu <feitianbubu@qq.com> Co-authored-by: Seefs <40468931+seefs001@users.noreply.github.com> Co-authored-by: undercat <93925665+chronicle12345@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: CaIon <i@caion.me> Co-authored-by: jimmyleocn <42566991+jimmyleocn@users.noreply.github.com> Co-authored-by: JY <397879704@qq.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Perfecto <kepengcheng314@gmail.com> Co-authored-by: Alear03030 <alear03030@gmail.com> Co-authored-by: 101Harry <33827520+heyrry@users.noreply.github.com> Co-authored-by: Wang <wangyanpeng03@gmail.com> Co-authored-by: markcheney1 <markcheney@163.com> Co-authored-by: Longtsing <songofsongs@vip.qq.com> Co-authored-by: longtsing <wangqinglong605504@cma.cn> Co-authored-by: Yorick <86869116+Yorick-Ryu@users.noreply.github.com> Co-authored-by: Kc <kc.harumeki@gmail.com> Co-authored-by: QuentinHsu <xuquentinyang@gmail.com> Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: spizzkid23 <spizzkid23@gmail.com>
6 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade the direct dependency and override to address GHSA-cg2g-xh64-v4q7.
Regenerate bun.lock with Bun and update the third-party license inventory.
English template:
.github/PULL_REQUEST_TEMPLATE/en.mdImportant
🔗 关联任务 / Related Issue
新功能请填写下方 Issue 编号;若还没有对应 Issue,请先自行创建。功能讨论请放在 Issue 中进行。
改动较大或方向性变更,请先在关联 Issue 中与维护者达成一致,再提交 PR。
Bug 修复请关联对应 Issue。设计取舍、理解偏差或预期不一致,更适合作为讨论或功能请求。
Closes #
🚀 变更类型 / Type of change
📝 变更描述 / Description
(简述做了什么、为什么生效。不得直接粘贴未经人工过滤的大段 AI 文本。如果难以简述,建议先拆分范围,或在 Issue 中与维护者对齐。)
更新依赖
📸 运行证明 / Proof of Work
(请写明如何验证:实际命令或步骤,以及观察结果。仅声明
go build通过或测试通过,不视为有效证明。UI 变更请附截图或录屏;Bug 修复请说明复现过程与修复后结果。)✅ 提交前检查项 / Checklist
New feature,我已关联对应 Issue;若尚无 Issue,我已先自行创建。go build通过或测试通过,不视为有效证明。