Skip to content

chore(deps): bump the runtime group across 1 directory with 5 updates - #46

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/runtime-93806fe27e
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/runtime-93806fe27e

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 1, 2026

Copy link
Copy Markdown
Contributor

Bumps the runtime group with 5 updates in the / directory:

Package From To
agency-orchestrator 0.19.2 0.21.1
express 5.2.1 5.3.0
msedge-tts 2.0.7 2.1.1
multer 2.4.0 2.5.0
zod 4.6.5 4.6.7

Updates agency-orchestrator from 0.19.2 to 0.21.1

Changelog

Sourced from agency-orchestrator's changelog.

[0.21.1] - 2026-10-21

Fixed

  • 桌面发布在生成校验文件前统一 GitHub 资产文件名,避免上传后空格变为点号导致下载文件名与 SHA256SUMS 不匹配;拒绝归一化重名。
  • 数据目录切换提示补上 role-libraries,避免手动迁移时遗漏按需下载的语言角色库(#44)。
  • Hermes 超过系统命令行长度上限的提示词改用官方 chat --query-file - --oneshot --format stream-json 协议完整传输,仅接受成功的最终 result;普通提示词保留 -z 兼容旧版,旧版不支持新协议时明确提示升级(#196)。

Added

  • 数据目录 IPC 与角色库安装新增离线集成测试:覆盖切换持久化、延后重启、取消/权限失败、恢复默认,以及角色库安装后跨应用目录识别、离线重试、完整性失败和残缺包清理(#44)。
  • 新增真实 Windows CI:覆盖 Hermes 超长提示词协议与 Electron 内置 Node 到外部兼容 Node 的 dsh 启动桥接;缺少或错误指定运行时会提前报错(#194)。测试使用本地 CLI 替身,不调用付费模型。

[0.21.0] - 2026-10-20

Fixed

  • 专家库明确区分专家内容语言与界面语言,切换与 URL 路由同步,清除旧语言筛选和预览,避免迟到的提示词请求覆盖新预览。
  • 移除运行详情弹层遮罩的背景模糊,避免流式更新时偶发整层闪烁(#193)。
  • Windows 新版 dsh npm 入口检查 Node 兼容性,内置运行时不兼容时探测系统 Node,支持 AO_CLI_NODE_PATH 指定;缺少兼容运行时提前报错,避免静默空输出。
  • CLI 启动时使用调用方传入的环境查找 Windows npm shim,避免与实际子进程 PATH 不一致;更新 dsh 空输出诊断,区分引擎运行时并说明新版入口的 Node 特性要求。
  • 更新 PackyCode 官网、Studio、远程供应商清单及 CLI 引导的注册推广链接。

Added

  • 新增赞助商星图 AstraFlow(UCloud ModelVerse)为内置供应商 astraflow(ASTRAFLOW_API_KEY,默认 https://api.modelverse.cn/v1, 海外节点用 ASTRAFLOW_BASE_URL 切):同一个 key 管对话(OpenAI 兼容)、出图(type: image,Seedream 走 /v1/images/generations) 与视频(type: video,新增 modelverse 任务形状:/v1/tasks/submit + /v1/tasks/status,已录 MiniMax-H3、Seedance 2.5)。 Studio 赞助商卡、Claude Code / Gemini CLI / Codex 中转预设、横幅轮换池与远程清单同步上架。端点均为无效 key 实测存在; 不设默认模型,建议模型取自公开的 /v1/models。视频首帧只收公网 URL(文档明示不收 Base64),本地图片在下单前即拒绝并说明。
  • Studio 人工输入新增当前问题查询和手动刷新;提交失败时核对状态、不自动重发,发送期间防止连点,保留当前问题草稿,并拒绝迟到查询覆盖新的问题或结束状态。
  • Studio 任务记录接入人工等待状态:收到问题进入等待、接受回答继续运行,支持等待期间取消;状态保存失败不阻塞输入,未回答就退出不会误记为成功。
  • Studio 人工输入按每次问题的随机标识校验,拒绝重复、过期和取消后的提交;单行 JSON 传输保留多行回答,重连回放清除已接收的问题。旧页面需刷新,服务重启后的等待恢复仍未实现。
  • Studio「我的运行」新增「任务记录」视图:查看最近 50 个任务、状态与保留事件,支持筛选和刷新;按当前实例的活动观察区分历史运行状态,读取失败时标注待确认。新任务显示工作流文件名,旧记录可兼容显示任务 ID。
  • Studio 工作流支持 clientRequestId 去重和 /api/jobs 查询;重复请求返回原任务 ID,避免再次启动引擎。启动失败、退出状态和显式取消会记录,启动日志与 start 事件不再回显完整命令参数。
  • 新增本地任务登记 API FileJobStore:持久 UUID、创建幂等、版本校验的状态转换与有界有序事件记录;状态和事件在同一文件中原子替换。同时接入 Studio 工作流启动、结束记录和查询接口;支持同一服务实例内后台运行和刷新重连,服务重启后的自动恢复仍未实现。 任务记录只是记账:记录损坏、目录不可写或被另一实例占用时,工作流照常运行(不进任务记录,运行日志里提示),不会因一条坏记录让 Studio 所有工作流都无法启动。
  • Studio 的 OpenAI-compatible 供应商配置新增高级模型参数:Thinking(默认/开启/关闭)、 reasoning effort(minimal 到 xhigh)与最大输出 tokens。配置保存在本机并真实透传到对话、提示词实验室、 自动组队、工作流运行和对比评测;Anthropic 原生协议、本地 CLI、Ollama 与纯视频供应商不会显示或误收这组参数。
  • 桌面端「设置 → 供应商」新增数据目录管理:显示并打开当前目录、用系统原生选择器切换、恢复默认, 校验目标可写后自动重启本地引擎。目录设置保存在固定的 Electron userData 中,AO_DATA_DIR 仍有最高优先级; 切换不会静默移动或删除旧目录,并明确列出需要手动复制的配置、工作流、历史产物与脚手架目录。

Security

  • undici 升级到已修复版本 6.29.x,消除 WebSocket 解压拒绝服务、未请求子协议拒绝服务和 retry interceptor 下游响应拆分问题;审计剩余项为无上游修复的 xlsx,以及需要跨版本评估的 pptxgenjs → image-size 传递依赖。

Fixed

  • Studio 刷新或关闭页面不再杀掉正在跑的工作流:每个运行在本机引擎里有一份事件缓冲,页面只是订阅者,断开即退订; 重新打开 Studio 会自动接回还在跑的运行(先重放全部事件再接实时输出,等待中的审批/输入框照样恢复)。 「停止」和关闭运行卡片改为显式取消(POST /api/run-cancel),引擎照常做中断存档、可续跑,任务记录为「已取消」。 离开页面时不再弹「确定离开?」。服务重启后旧运行不在内存里,到「我的运行」查看存档。专家单问仍是断开即停。

... (truncated)

Commits
  • fa48407 fix: align release checksums with GitHub asset names
  • 4dffecb release: prepare engine 0.21.1 and desktop 0.4.14 with issue fixes
  • c48a29c docs: record successful manual SignPath application submission
  • adad80e docs: clarify SignPath account names and manual registration handoff
  • a6e9817 docs: prepare SignPath application and disclose signing requirements
  • 38afe19 docs: record issue validation results and remaining acceptance
  • 7da1489 fix: support oversized Hermes prompts and verify Windows CLI runtime
  • 3314229 fix(website): clarify and synchronize expert library languages
  • fddfe69 chore(release): prepare engine 0.21.0 and desktop 0.4.13
  • 4bad1f4 fix(studio): remove backdrop blur from run viewer (#193)
  • Additional commits viewable in compare view

Updates express from 5.2.1 to 5.3.0

Release notes

Sourced from express's releases.

v5.3.0

Highlights

🐞 Bug fixes

  • Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by @​YuryShkoda in #4893

    Fixed the behavior of res.send() to prevent conflicts between Content-Length and Transfer-Encoding HTTP headers in responses. The Content-Length header in res.send() is now only added when a Transfer-Encoding header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a Transfer-Encoding header - by @​cuishuang in #7459

🚀 Improvements

  • Allow conditional revalidation for QUERY requests. req.fresh previously only validated freshness for GET and HEAD requests, so QUERY responses never returned 304 despite a matching validator. Since QUERY is a safe, idempotent, and cacheable method that supports conditional requests, it is now included in the freshness check - by @​Cherry in #7366

    // QUERY /reports with If-None-Match: "12345"
    app.query('/reports', (req, res) => {
      res.set('ETag', '"12345"');
      res.send(results); // now responds 304 Not Modified
    });
  • Improve HTML structure in res.redirect() responses when HTML format is accepted by adding <!DOCTYPE html>, <title>, and <body> tags for better browser compatibility - by @​Bernice55231 in #5167

  • When calling app.render with options set to null, the locals object is handled correctly, preventing unexpected errors and making the method behave the same as when options is omitted or an empty object is passed - by AkaHarshit in #6903

    app.render('index', null, callback); // now works as expected
  • Upgrade content-type to ^2.0.0, bringing a faster parser (~1.5x quicker Content-Type parsing/formatting in res.send()) along with a behavior change: res.send() now keeps any existing parameters when adding the charset and no longer throws on a Content-Type that fails to parse. type-is is upgraded to ^2.1.0 as part of the same change - by @​blakeembrey in #7234

    res.set('Content-Type', 'text/plain; foo=bar').send('hey');
    // -> Content-Type: text/plain; foo=bar; charset=utf-8
  • The default error handler now logs the full error object instead of only its stack trace, so nested details such as Error.cause and library-specific properties (e.g. Sequelize's parent/original) are no longer swallowed - by @​Nitin-Mohapatra in #6464

  • Upgrade content-disposition to ^2.0.1, which changes the Content-Disposition header emitted by res.download(), res.attachment(), and res.sendFile(): file names that are valid HTTP tokens are no longer wrapped in quotes. This is equivalent per RFC 6266, but applications asserting on the exact header bytes should update their expectations - by @​blakeembrey in #7233

    res.attachment('user.html');
    // before -> Content-Disposition: attachment; filename="user.html"
    // after  -> Content-Disposition: attachment; filename=user.html

... (truncated)

Changelog

Sourced from express's changelog.

5.3.0

🐞 Bug fixes

  • Fixed HTTP header conflict between Content-Length and Transfer-Encoding in res.send - by @​YuryShkoda in #4893

    Fixed the behavior of res.send() to prevent conflicts between Content-Length and Transfer-Encoding HTTP headers in responses. The Content-Length header in res.send() is now only added when a Transfer-Encoding header is not present, complying with the HTTP specification that states both headers should not coexist in the same response. ETag generation is unaffected by the presence of a Transfer-Encoding header - by @​cuishuang in #7459

🚀 Improvements

  • Allow conditional revalidation for QUERY requests. req.fresh previously only validated freshness for GET and HEAD requests, so QUERY responses never returned 304 despite a matching validator. Since QUERY is a safe, idempotent, and cacheable method that supports conditional requests, it is now included in the freshness check - by @​Cherry in #7366

    // QUERY /reports with If-None-Match: "12345"
    app.query('/reports', (req, res) => {
      res.set('ETag', '"12345"');
      res.send(results); // now responds 304 Not Modified
    });
  • Improve HTML structure in res.redirect() responses when HTML format is accepted by adding <!DOCTYPE html>, <title>, and <body> tags for better browser compatibility - by @​Bernice55231 in #5167

  • When calling app.render with options set to null, the locals object is handled correctly, preventing unexpected errors and making the method behave the same as when options is omitted or an empty object is passed - by AkaHarshit in #6903

    app.render('index', null, callback); // now works as expected
  • Upgrade content-type to ^2.0.0, bringing a faster parser (~1.5x quicker Content-Type parsing/formatting in res.send()) along with a behavior change: res.send() now keeps any existing parameters when adding the charset and no longer throws on a Content-Type that fails to parse. type-is is upgraded to ^2.1.0 as part of the same change - by @​blakeembrey in #7234

    res.set('Content-Type', 'text/plain; foo=bar').send('hey');
    // -> Content-Type: text/plain; foo=bar; charset=utf-8
  • The default error handler now logs the full error object instead of only its stack trace, so nested details such as Error.cause and library-specific properties (e.g. Sequelize's parent/original) are no longer swallowed - by @​Nitin-Mohapatra in #6464

  • Upgrade content-disposition to ^2.0.1, which changes the Content-Disposition header emitted by res.download(), res.attachment(), and res.sendFile(): file names that are valid HTTP tokens are no longer wrapped in quotes. This is equivalent per RFC 6266, but applications asserting on the exact header bytes should update their expectations - by @​blakeembrey in #7233

    res.attachment('user.html');
    // before -> Content-Disposition: attachment; filename="user.html"
    // after  -> Content-Disposition: attachment; filename=user.html

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for express since your current version.


Updates msedge-tts from 2.0.7 to 2.1.1

Commits

Updates multer from 2.4.0 to 2.5.0

Release notes

Sourced from multer's releases.

v2.5.0

Important: Security

What's Changed

New Contributors

Full Changelog: expressjs/multer@v2.4.0...v2.5.0

Changelog

Sourced from multer's changelog.

2.5.0

  • Fix CVE-2026-113872 (GHSA-q7qp-rjg7-q26m)
  • Accept a field value of exactly limits.fieldSize bytes, so LIMIT_FIELD_VALUE fires only when the limit is exceeded. This also covers the default fieldSize of 1MB, so a 1048576 byte value is no longer rejected when you set no limits. If you set fieldSize one higher to work around this, you can drop the extra one (#1481)
  • Do not add a file to the abort cleanup list when its storage engine reports an error after a LIMIT_FILE_SIZE abort; DiskStorage no longer tries to unlink an undefined path (#1489)
Commits
  • 2c380d0 2.5.0 (#1490)
  • 80a2d9d fix: swallow late busboy error after teardown
  • c901d48 chore(deps): bump github/codeql-action/analyze to 4.38.2 (#1486)
  • ba3619a chore(deps): bump github/codeql-action/upload-sarif (#1487)
  • 0b72081 chore(deps): bump github/codeql-action/init to 4.38.2 (#1488)
  • 7661ce7 fix: allow a field value exactly at the fieldSize limit (#1481)
  • 6dac92f fix: don't add a failed upload to the abort cleanup list (#1489)
  • dd9f062 docs: fix typo in .none() and grammar in .any() (#1485)
  • See full diff in compare view

Updates zod from 4.6.5 to 4.6.7

Release notes

Sourced from zod's releases.

v4.6.7

Commits:

  • b500a2ee95134f81d74da7911d7378dd2853d042 4.6.7

v4.6.6

Six malicious commits pushed to main on September 21 with a compromised git credential were reverted the same day in #6620 and have since been removed from the history of main. None were ever published to npm. The npm provenance for 4.6.6 names 284243fb, the pre-rewrite copy of 9c219833 with identical contents.

Commits:

  • 0cd3af5e9f50ad11bbcd4407a46a21b8848ba574 docs: load the en locale directly in Zod Mini
  • 9d5e60f162997b764b40d45aa02481888db50dea docs: import locales from zod/locales, not z.locales
  • 34a626f307871ecbb0123947559328dc52ed5e3e docs: tighten the z.locales tree-shaking note
  • 74304ce5b5796b5edb9a88ceb8e170b6ea3e82df release: stage npm versions instead of publishing them (#6622)
  • b2ef983e0711ff6517d6020b021071e2e5653efa docs: add Code for Japan to bronze sponsors
  • 8fb2faf0584828a6a027d8279db36f6f52784462 docs: crop the Code for Japan logo and list it first in bronze
  • bacad518c41610d654658172d325874bf0ee6290 docs: square the Code for Japan logo to match the other bronze tiles
  • c42596bd1c87e941d7241d10e012c5c196adcc10 release: hold the run on the release-approval environment until the staged versions are approved (#6638)
  • a2ba4a67986a3e6b2b131be30084a2f460d9ea67 fix(types): declare record output and input as members, not base type arguments (#6645)
  • a0ebf970f2d752e5f58527cd2942ff48be4f46bd fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • 529f78dd9431b07f49647fee3aa0819b3f8b66b7 4.6.6
  • 9c219833c3a3764fa1f1ea9c5ecec8254a63c0b1 ci: stage at verbose so a failed OIDC token exchange says why
Commits
  • b500a2e 4.6.7
  • 9c21983 ci: stage at verbose so a failed OIDC token exchange says why
  • 529f78d 4.6.6
  • a0ebf97 fix(v4): check array, set and map size bounds before parsing elements (#6652)
  • a2ba4a6 fix(types): declare record output and input as members, not base type argumen...
  • c42596b release: hold the run on the release-approval environment until the staged ve...
  • bacad51 docs: square the Code for Japan logo to match the other bronze tiles
  • 8fb2faf docs: crop the Code for Japan logo and list it first in bronze
  • b2ef983 docs: add Code for Japan to bronze sponsors
  • 74304ce release: stage npm versions instead of publishing them (#6622)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps the runtime group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [agency-orchestrator](https://github.com/jnMetaCode/agency-orchestrator) | `0.19.2` | `0.21.1` |
| [express](https://github.com/expressjs/express) | `5.2.1` | `5.3.0` |
| [msedge-tts](https://github.com/Migushthe2nd/MsEdgeTTS) | `2.0.7` | `2.1.1` |
| [multer](https://github.com/expressjs/multer) | `2.4.0` | `2.5.0` |
| [zod](https://github.com/colinhacks/zod) | `4.6.5` | `4.6.7` |



Updates `agency-orchestrator` from 0.19.2 to 0.21.1
- [Release notes](https://github.com/jnMetaCode/agency-orchestrator/releases)
- [Changelog](https://github.com/jnMetaCode/agency-orchestrator/blob/main/CHANGELOG.md)
- [Commits](jnMetaCode/agency-orchestrator@v0.19.2...v0.21.1)

Updates `express` from 5.2.1 to 5.3.0
- [Release notes](https://github.com/expressjs/express/releases)
- [Changelog](https://github.com/expressjs/express/blob/master/History.md)
- [Commits](expressjs/express@v5.2.1...v5.3.0)

Updates `msedge-tts` from 2.0.7 to 2.1.1
- [Commits](https://github.com/Migushthe2nd/MsEdgeTTS/commits)

Updates `multer` from 2.4.0 to 2.5.0
- [Release notes](https://github.com/expressjs/multer/releases)
- [Changelog](https://github.com/expressjs/multer/blob/main/CHANGELOG.md)
- [Commits](expressjs/multer@v2.4.0...v2.5.0)

Updates `zod` from 4.6.5 to 4.6.7
- [Release notes](https://github.com/colinhacks/zod/releases)
- [Commits](colinhacks/zod@v4.6.5...v4.6.7)

---
updated-dependencies:
- dependency-name: agency-orchestrator
  dependency-version: 0.21.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: runtime
- dependency-name: express
  dependency-version: 5.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: runtime
- dependency-name: msedge-tts
  dependency-version: 2.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: runtime
- dependency-name: multer
  dependency-version: 2.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: runtime
- dependency-name: zod
  dependency-version: 4.6.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: runtime
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 1, 2026

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants