openxiangda 2.59.2 → 2.59.3-http.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/browser/components/platform-fields/SignatureField.d.ts.map +1 -1
- package/dist/browser/components/platform-fields/SignatureField.js +2 -4
- package/dist/browser/components/platform-fields/SignatureField.js.map +1 -1
- package/dist/browser/sha256.d.ts +3 -0
- package/dist/browser/sha256.d.ts.map +1 -0
- package/dist/browser/sha256.js +10 -0
- package/dist/browser/sha256.js.map +1 -0
- package/dist/browser/workflow-task-command-recovery.d.ts.map +1 -1
- package/dist/browser/workflow-task-command-recovery.js +2 -2
- package/dist/browser/workflow-task-command-recovery.js.map +1 -1
- package/documentation/getting-started.md +7 -7
- package/documentation/manifest.json +2 -2
- package/package.json +17 -20
- package/releases/2.0.0.json +50 -0
- package/releases/2.0.1.json +39 -0
- package/releases/2.1.0.json +44 -0
- package/releases/2.1.1.json +48 -0
- package/releases/2.10.0.json +42 -0
- package/releases/2.11.0.json +41 -0
- package/releases/2.12.0.json +38 -0
- package/releases/2.13.0.json +41 -0
- package/releases/2.13.1.json +33 -0
- package/releases/2.13.2.json +31 -0
- package/releases/2.14.0.json +41 -0
- package/releases/2.15.0.json +40 -0
- package/releases/2.16.0.json +41 -0
- package/releases/2.17.0.json +39 -0
- package/releases/2.17.1.json +34 -0
- package/releases/2.18.0.json +37 -0
- package/releases/2.18.1.json +31 -0
- package/releases/2.18.10.json +29 -0
- package/releases/2.18.2.json +30 -0
- package/releases/2.18.3.json +30 -0
- package/releases/2.18.9.json +37 -0
- package/releases/2.19.0.json +38 -0
- package/releases/2.2.0.json +48 -0
- package/releases/2.2.1.json +35 -0
- package/releases/2.2.2.json +34 -0
- package/releases/2.20.0.json +36 -0
- package/releases/2.20.1.json +30 -0
- package/releases/2.20.4.json +30 -0
- package/releases/2.21.0.json +35 -0
- package/releases/2.21.1.json +36 -0
- package/releases/2.21.2.json +34 -0
- package/releases/2.21.3.json +31 -0
- package/releases/2.21.4.json +31 -0
- package/releases/2.22.0.json +35 -0
- package/releases/2.22.1.json +32 -0
- package/releases/2.22.2.json +35 -0
- package/releases/2.22.3.json +32 -0
- package/releases/2.22.4.json +33 -0
- package/releases/2.22.5.json +31 -0
- package/releases/2.22.6.json +29 -0
- package/releases/2.22.7.json +29 -0
- package/releases/2.23.0.json +34 -0
- package/releases/2.24.0.json +33 -0
- package/releases/2.24.1.json +33 -0
- package/releases/2.24.2.json +31 -0
- package/releases/2.24.3.json +33 -0
- package/releases/2.25.0.json +31 -0
- package/releases/2.25.1.json +33 -0
- package/releases/2.25.2.json +32 -0
- package/releases/2.25.3.json +32 -0
- package/releases/2.26.0.json +41 -0
- package/releases/2.27.0.json +38 -0
- package/releases/2.28.0.json +37 -0
- package/releases/2.28.1.json +34 -0
- package/releases/2.29.0.json +37 -0
- package/releases/2.29.1.json +34 -0
- package/releases/2.29.2.json +32 -0
- package/releases/2.3.0.json +37 -0
- package/releases/2.30.0.json +34 -0
- package/releases/2.31.0.json +39 -0
- package/releases/2.31.1.json +38 -0
- package/releases/2.31.2.json +34 -0
- package/releases/2.31.3.json +32 -0
- package/releases/2.31.4.json +33 -0
- package/releases/2.31.5.json +33 -0
- package/releases/2.31.6.json +29 -0
- package/releases/2.31.7.json +29 -0
- package/releases/2.31.8.json +33 -0
- package/releases/2.31.9.json +33 -0
- package/releases/2.32.0.json +38 -0
- package/releases/2.33.0.json +33 -0
- package/releases/2.34.0.json +38 -0
- package/releases/2.34.1.json +34 -0
- package/releases/2.34.2.json +36 -0
- package/releases/2.34.3.json +35 -0
- package/releases/2.35.0.json +42 -0
- package/releases/2.35.1.json +43 -0
- package/releases/2.35.2.json +45 -0
- package/releases/2.35.3.json +46 -0
- package/releases/2.36.0.json +38 -0
- package/releases/2.36.1.json +33 -0
- package/releases/2.37.0.json +39 -0
- package/releases/2.37.1.json +33 -0
- package/releases/2.37.2.json +31 -0
- package/releases/2.38.0.json +40 -0
- package/releases/2.39.0.json +37 -0
- package/releases/2.39.1.json +32 -0
- package/releases/2.4.0.json +37 -0
- package/releases/2.4.1.json +35 -0
- package/releases/2.40.0.json +38 -0
- package/releases/2.40.1.json +30 -0
- package/releases/2.41.0.json +39 -0
- package/releases/2.41.1.json +33 -0
- package/releases/2.41.2.json +34 -0
- package/releases/2.42.0.json +36 -0
- package/releases/2.43.0.json +38 -0
- package/releases/2.44.0.json +36 -0
- package/releases/2.44.1.json +33 -0
- package/releases/2.45.0.json +35 -0
- package/releases/2.46.0.json +35 -0
- package/releases/2.46.1.json +30 -0
- package/releases/2.46.2.json +29 -0
- package/releases/2.46.3.json +30 -0
- package/releases/2.47.0.json +34 -0
- package/releases/2.47.1.json +31 -0
- package/releases/2.47.2.json +28 -0
- package/releases/2.47.3.json +29 -0
- package/releases/2.47.4.json +29 -0
- package/releases/2.47.5.json +29 -0
- package/releases/2.48.0.json +33 -0
- package/releases/2.48.1.json +30 -0
- package/releases/2.48.2.json +29 -0
- package/releases/2.48.3.json +32 -0
- package/releases/2.48.4.json +31 -0
- package/releases/2.49.0.json +35 -0
- package/releases/2.49.1.json +32 -0
- package/releases/2.49.10.json +34 -0
- package/releases/2.49.11.json +30 -0
- package/releases/2.49.12.json +30 -0
- package/releases/2.49.13.json +29 -0
- package/releases/2.49.14.json +30 -0
- package/releases/2.49.2.json +31 -0
- package/releases/2.49.3.json +31 -0
- package/releases/2.49.4.json +30 -0
- package/releases/2.49.5.json +31 -0
- package/releases/2.49.6.json +30 -0
- package/releases/2.49.8.json +33 -0
- package/releases/2.49.9.json +35 -0
- package/releases/2.5.0.json +37 -0
- package/releases/2.50.0.json +32 -0
- package/releases/2.52.0.json +34 -0
- package/releases/2.53.0.json +34 -0
- package/releases/2.54.0.json +35 -0
- package/releases/2.54.1.json +29 -0
- package/releases/2.55.2.json +31 -0
- package/releases/2.55.3.json +32 -0
- package/releases/2.55.4.json +30 -0
- package/releases/2.56.0.json +32 -0
- package/releases/2.57.0.json +35 -0
- package/releases/2.59.3.json +36 -0
- package/releases/2.59.4.json +38 -0
- package/releases/2.59.5.json +40 -0
- package/releases/2.59.6.json +30 -0
- package/releases/2.59.7.json +32 -0
- package/releases/2.6.0.json +37 -0
- package/releases/2.7.0.json +37 -0
- package/releases/2.7.1.json +31 -0
- package/releases/2.8.0.json +32 -0
- package/releases/2.8.1.json +30 -0
- package/releases/2.9.0.json +33 -0
- package/releases/2.9.1.json +31 -0
- package/releases/2.9.2.json +33 -0
- package/releases/2.9.3.json +31 -0
- package/releases/2.9.4.json +37 -0
- package/skills/manifest.json +1 -1
- package/skills/openxiangda-v2/SKILL.md +4 -4
- package/skills/openxiangda-v2/references/getting-started.md +7 -7
- package/releases/2.55.1.json +0 -32
- package/releases/2.55.6.json +0 -32
- package/releases/2.57.1.json +0 -31
- package/releases/2.59.0.json +0 -36
- package/releases/2.59.1.json +0 -37
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.30.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.30.0:平台条件唯一键",
|
|
6
|
+
"summary": "模型可声明条件唯一键,统一约束普通 CRUD、导入和业务事务;编译器在发布前检查规则并识别目标平台是否支持。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型与数据资源支持有界 uniqueKeys 声明,可选择精确比较、NFKC 空白折叠或 ASCII 大写,并按文本空值或单选集合限定参与记录。",
|
|
9
|
+
"两端编译器、JSON Schema、声明诊断和能力清单使用一致契约,自动要求 data.unique-keys@1.0.0。未声明的模型不增加能力要求。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要跨并发写入保障业务编号或复合字段唯一性的 OpenXiangda 2.0 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"更新到 openxiangda@2.30.0 并更新锁文件;在需要唯一性的模型声明 uniqueKeys,使用当前版本的数据与权限文档。",
|
|
17
|
+
"先确认目标平台实际提供 data.unique-keys@1.0.0,再激活测试版本。历史重复或超长数据会明确拒绝激活并保留原环境。",
|
|
18
|
+
"重复写入处理 HTTP 409 和规则标识;长度超限处理 HTTP 422。避免盲目重试创建,事务失败后按原业务状态恢复。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"每资源最多 8 条、每条 1–4 个键字段和最多 4 个 AND 条件;参与比较字段归一化后最多 256 个 UTF-8 字节。",
|
|
22
|
+
"已有规则的修改、删除和所用字段替换需要平台受管迁移;连接开发不能私自改变规则。",
|
|
23
|
+
"平台升级与 SDK 发行分别验收;npm 发行不代表客户节点已经上线。跨 PostgreSQL 大版本变更须先安排归一化索引的受管重建。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"workspaceGenerations": "v2",
|
|
29
|
+
"platform": "声明规则时要求 data.unique-keys@1.0.0;普通应用沿用现有能力。",
|
|
30
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "cbe1a5766e0cc0d8948d54b6d2129320b5d2fbe1e8f7120874b9f56c774b1fcb",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.30.0"
|
|
34
|
+
}
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.0:缓存、排队与原子配额",
|
|
6
|
+
"summary": "应用可声明热点内容缓存、全局准入、可恢复的 Native 命令和整数配额。平台承担回源保护、受理幂等与事务内分配,React 和移动端 SDK 提供等待、提交及原结果恢复。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"data.concurrency 由两端共享编译器验证,缓存读取声明包含权限范围、有限参数、失效依赖和回源预算。",
|
|
9
|
+
"等待准入按可信主体合并重复请求,持久命令返回原操作回执,响应丢失和页面刷新后可继续核对结果。",
|
|
10
|
+
"整数配额支持立即分配、预占、确认、释放与到期;配额、业务记录、事件和结果在同一 Native 事务提交,受管模型阻止普通 CRUD 绕过。",
|
|
11
|
+
"openxiangda/react 和 openxiangda/mobile 提供 createManagedConcurrencyClient、useManagedCommand、ManagedCommandStatus 与 ManagedCommandGate。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"需要缓存、排队、限量申领、预约或抢票的 OpenXiangda 2.0 应用开发者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"升级到 openxiangda@2.31.0 并更新锁文件,按 docs/managed-concurrency.md 及完整声明示例配置资源和权限。",
|
|
19
|
+
"先确认目标平台已部署 data.managed-concurrency@1.0.0 及对应 SQL migration,再激活测试版本。未启用此声明的应用沿用原路径。",
|
|
20
|
+
"上线前按目标硬件、真实权限和业务规模验证完成速率、P95/P99、回源 SQL、锁等待及恢复时间;部署和容量验收独立于 npm 发行。",
|
|
21
|
+
"停用或切换不兼容版本前停止新受理并排空非终态命令,保留历史命令、分配及回执。"
|
|
22
|
+
],
|
|
23
|
+
"knownLimitations": [
|
|
24
|
+
"首版执行编译后的 Native 原子动作,不把任意 JS、SQL 或第三方调用纳入原子事务。",
|
|
25
|
+
"Redis 故障时暂停新准入和缓存回源;临时等待位置不承诺持久,已持久受理命令可恢复。",
|
|
26
|
+
"缓存减少内容 SQL,当前身份和权限链路仍有数据库访问;不提供公共 CDN 发布或自动全量预热。",
|
|
27
|
+
"同一配额池和主体永久去重,释放后不会自动重新报名;新一轮业务使用新的权威资源或配额池。",
|
|
28
|
+
"资源保护上限不代表生产吞吐保证;公开包升级不会自动升级客户平台。"
|
|
29
|
+
],
|
|
30
|
+
"issues": [],
|
|
31
|
+
"compatibility": {
|
|
32
|
+
"node": ">=24",
|
|
33
|
+
"workspaceGenerations": "v2",
|
|
34
|
+
"platform": "声明并发能力时要求 data.managed-concurrency@1.0.0;同时声明业务唯一键时还要求 data.unique-keys@1.0.0。",
|
|
35
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
36
|
+
},
|
|
37
|
+
"sha256": "6258bae64bad0db43a319ecb6886a037952e0c77410edd6a790d18b8cd470645",
|
|
38
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.0"
|
|
39
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.1:应用业务 Agent 任务声明",
|
|
6
|
+
"summary": "应用可以在现有 AI 操作上显式声明面向普通用户的业务任务、常见问法、只读辅助能力和输入字段查询绑定。编译器把这些信息并入同一个 AppVersion AI Catalog,平台按当前用户权限发现和执行。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"ai.agent.visibility 区分可独立办理的 task 与任务引用的只读 support;未声明的底层 CRUD 不自动成为普通用户任务。",
|
|
9
|
+
"任务可以声明 examples、aliases、supportOperations 和 inputLookups;编译器校验辅助操作只读、引用闭合和请求字段存在。",
|
|
10
|
+
"docs/backend.md、声明速查和 OpenXiangda 2.0 Skill 提供接入流程及访客预约示例。",
|
|
11
|
+
"并发能力前端指南覆盖热点读取、申请、排队、预占确认与原结果恢复,并标明已提供 API 和待实现封装。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"希望把业务操作接入平台助手或应用 Agent 的 OpenXiangda 2.0 应用开发者。",
|
|
16
|
+
"需要实现缓存、排队或限额场景前端的应用开发者。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"升级到 openxiangda@2.31.1 并更新锁文件,先实现完整业务操作、授权和只读辅助查询,再按 docs/backend.md 声明 ai.agent。",
|
|
20
|
+
"在测试环境运行 check 与完整输入、缺失输入、同名对象、权限不足和重复提交场景;发布应用版本后核对 AI Catalog 摘要与当前环境 Head。",
|
|
21
|
+
"平台服务端须部署支持显式业务任务发现的版本;npm 包发布本身不会升级平台或自动公开旧应用操作。",
|
|
22
|
+
"并发前端接入按 docs/managed-concurrency-frontend.md 选择模式,先核对已导出的 API 与目标平台能力。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"本次包仅增加业务任务元数据与编译校验;交互卡片资源、持久 Interaction 和 MCP Apps Host 由后续平台与应用批次交付。",
|
|
26
|
+
"现有独立 MCP Facade 的写入预览与确认协议保持原样;平台自有 Agent 的自动写入由平台执行层和权限边界负责。",
|
|
27
|
+
"旧应用的底层 CRUD 不会自动转换为普通用户任务,需应用维护者完成业务语义与辅助能力接入。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"workspaceGenerations": "v2",
|
|
33
|
+
"platform": "平台业务 Agent 任务发现需配套部署支持 ai.agent 元数据的服务端版本。",
|
|
34
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "37c61ac4c9b17a8ca688cc9e1f38f4ed106754a7342e1a6aa9b2095e954a5118",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.1"
|
|
38
|
+
}
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.2:普通业务任务可自动执行写入",
|
|
6
|
+
"summary": "应用可为普通业务写任务显式声明免通用二次确认。用户明确要求办理且信息完整时,平台 Agent 可直接执行并返回回执;权限、版本绑定与幂等仍由平台和应用校验。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"backend.operations[].ai.confirmation 支持普通 write 显式选择 none;省略时仍为 required。",
|
|
9
|
+
"编译器、Catalog 契约、应用开发指南及 Skill 同步说明确认策略。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"开发预约、报修等普通业务 Agent 写任务的 OpenXiangda 2.0 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级到 openxiangda@2.31.2 并更新锁文件,在业务操作的 ai 声明中按需显式设置 confirmation: 'none'。",
|
|
17
|
+
"在预发验证完整输入、缺失输入、对象歧义、无权访问和同一幂等键重放,再发布应用版本并核对 Catalog 与环境 Head。",
|
|
18
|
+
"平台 Agent 执行层须支持受管直接执行;npm 包发布本身不更新平台。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"免确认仅适用于普通 write;destructive 和 external 继续要求确认,read 不确认。",
|
|
22
|
+
"独立 MCP Facade 的预览/确认协议未在本轮改变。",
|
|
23
|
+
"交互卡片资源与持久 Interaction 仍需后续批次交付。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"workspaceGenerations": "v2",
|
|
29
|
+
"platform": "需配套支持业务 Agent 受管直接执行的服务端版本。",
|
|
30
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "be6fa650ee197a3949c17aec11af97e833e70a1d8461992c3e25063c238cff1e",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.2"
|
|
34
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.3:业务 Agent 结果卡片声明",
|
|
6
|
+
"summary": "应用任务可以声明已完成操作的只读结果卡片。编译器把展示字段限制在响应 Schema 的顶层标量属性,并将声明随应用版本发布。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"backend.operations[].ai.agent.resultCard 支持标题和最多 8 个结果字段,并校验字段引用、类型及边界。",
|
|
9
|
+
"开发文档、速查表与 AI Skill 同步给出结果卡片示例和接入规则。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要在平台助手会话中展示预约、报修等业务回执的 OpenXiangda 2.0 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级 openxiangda 并更新锁文件;在业务操作的 responseSchema.properties 中声明可展示的标量字段,再可选配置 agent.resultCard。",
|
|
17
|
+
"在预发验证完整业务结果、字段缺失和刷新恢复;卡片展示需要配套平台服务端与前端版本。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"本版只定义已完成业务操作的只读结果卡片;待补信息表单、持久 Interaction 与应用自定义 React Host 尚未发布。",
|
|
21
|
+
"结果卡片不改变应用权限、业务执行或既有 MCP Facade 的确认协议。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"workspaceGenerations": "v2",
|
|
27
|
+
"platform": "结果卡片呈现需要配套平台 Agent 回执投影和会话前端。",
|
|
28
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
29
|
+
},
|
|
30
|
+
"sha256": "56e36516118cda6a6d2d4029dc25e593a1b4e76198279cf27cf9e58bf8dc392e",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.3"
|
|
32
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.4",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.4:业务 Agent 标准填写卡片声明",
|
|
6
|
+
"summary": "应用任务可以声明有界填写卡片;平台助手在缺少信息或业务选项有歧义时让用户续填,并将提交绑定到已发布的固定业务能力。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"backend.operations[].ai.agent.inputCard 支持短文本、多行文本和只读选项,编译器检查必填字段、控件类型、选项响应 Schema 和执行策略。",
|
|
9
|
+
"开发文档、声明速查表与 AI Skill 同步说明填写卡片、辅助查询和业务 handler 的接入规则。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要让普通用户在平台助手会话中补齐报修、预约等业务参数的 OpenXiangda 2.0 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级 openxiangda 并更新锁文件;先实现有权限和幂等保障的业务操作,再为同一操作声明包含全部必填字段的 agent.inputCard。",
|
|
17
|
+
"选择控件绑定同应用只读辅助操作,响应明确声明最多 20 项的 items[{value,label}];在预发验证刷新续填、重复提交、权限拒绝和真实业务回读。",
|
|
18
|
+
"平台服务端、Worker、数据库迁移和会话前端需要配套发布后,填写卡片才会在对话中出现。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"首版只有平台标准控件;应用自定义 React 卡片 Host/SDK 是后续独立单元。",
|
|
22
|
+
"填写卡片只适用于已显式开放、免通用二次确认的普通写任务;破坏性和外部动作仍需独立确认协议。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "填写和续接需要配套 Agent Interaction 服务、Worker、SQL 迁移与 SSE 前端。",
|
|
29
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "d025a3b8411a27ab3259f1b3272ff551b3856c9d121f4cb3bdfda9a821760b83",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.4"
|
|
33
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.5",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.5:应用 Agent 自定义卡片",
|
|
6
|
+
"summary": "应用可以把填写卡和结果卡的自定义脚本随同一发布版本交付,由平台在隔离卡片 Host 中展示。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"ai.agent.inputCard 和 resultCard 可声明受限的 agent-cards/*.js 资源;发布时核验脚本进入同一前端制品。",
|
|
9
|
+
"openxiangda/agent-card SDK 提供状态接收、只读选项查询、固定任务提交和尺寸同步;中文开发资料与 Skill 给出构建和验收示例。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要在平台业务 Agent 中展示应用自有填写或结果布局的 OpenXiangda 2.0 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级 openxiangda 并更新锁文件;保留标准 inputCard/resultCard 字段声明作为资源失败时的回退。",
|
|
17
|
+
"将使用 SDK 的卡片构建为单文件 IIFE 放入前端 dist/agent-cards/,配置对应 resource,然后运行 check 与预发 deploy。",
|
|
18
|
+
"确认平台已发布配套 Agent 卡片资源端点与隔离 Host;在预发验证歧义选择、刷新、重复提交、权限拒绝与业务回读。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"首版消息桥是平台限定协议,不宣称与官方 MCP Apps 线级兼容;卡片只支持已声明的选项查询和固定提交。",
|
|
22
|
+
"结果卡只收到已声明的标量字段;复杂列表、附件和额外工具调用仍需后续独立契约。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "自定义卡片需要配套 Agent Center 资源解析服务和无同源 iframe Host。",
|
|
29
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "b674dd23dcb5fc9e00a7af758f01291295c78b8b6756b43d5f678ba79e4df345",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.5"
|
|
33
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.6",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.6:补充 Agent 卡片浏览器构建规范",
|
|
6
|
+
"summary": "明确自定义 Agent 卡片的浏览器独立运行要求,防止脚本构建成功但在隔离 iframe 中无法显示。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"Vite 单文件 IIFE 示例明确替换 process.env.NODE_ENV,并要求在无同源 sandbox 与 CSP 下验证卡片握手和提交消息。"
|
|
10
|
+
],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"开发应用 Agent 自定义卡片的 OpenXiangda 2.0 应用开发者。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"在卡片专用 Vite 配置中加入示例的生产环境替换,重新构建并在隔离浏览器 iframe 中验收。"
|
|
16
|
+
],
|
|
17
|
+
"knownLimitations": [
|
|
18
|
+
"本版只补充构建文档;卡片消息桥仍为平台限定协议。"
|
|
19
|
+
],
|
|
20
|
+
"issues": [],
|
|
21
|
+
"compatibility": {
|
|
22
|
+
"node": ">=24",
|
|
23
|
+
"workspaceGenerations": "v2",
|
|
24
|
+
"platform": "沿用已发布的 Agent Center 卡片资源解析服务和 iframe Host。",
|
|
25
|
+
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "3e1ffae9d677ad5c0c5e70030f34067bdc76c5751afe7045a77b51d40f641cad",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.6"
|
|
29
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.7",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.7:后端受控核验所选组织人员",
|
|
6
|
+
"summary": "应用后端可在已声明的业务操作内核验所选人员,姓名、工号与部门由平台组织架构提供。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"增加 selected-user 目录声明和 BusinessDirectoryService.selectedUser,按声明投影组织身份字段并返回核验快照。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"需要管理员代录、身份纠正或针对所选组织人员执行业务操作的 V2 应用。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"升级应用工具链,并先部署支持 directory.selected-user 1.0.0 的平台;在具体后端操作声明所需字段和目录读取权限。"
|
|
16
|
+
],
|
|
17
|
+
"knownLimitations": [
|
|
18
|
+
"只支持同租户有效组织人员;未声明能力、无目录权限或人员不可用时明确拒绝。"
|
|
19
|
+
],
|
|
20
|
+
"issues": [],
|
|
21
|
+
"compatibility": {
|
|
22
|
+
"node": ">=24",
|
|
23
|
+
"workspaceGenerations": "v2",
|
|
24
|
+
"platform": "新增能力需要支持 directory.selected-user 1.0.0 的平台;既有 current-initiator 行为不变。",
|
|
25
|
+
"v1": "独立 V1 引擎不受影响。"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "8843f2ad58d915c2b9158821b6640bc4453a5e0e6f6066d918fda0e9dc168ccd",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.7"
|
|
29
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.8",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.8:富文本图片与原通知投递恢复",
|
|
6
|
+
"summary": "支持具名动作的富文本托管图片,并公开按原消息查询、恢复失败投递的用户态接口。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"NotificationService 增加 listMessages、listDeadLetters、replayDeadLetter,固定应用环境并保留平台管理权限。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"managedFiles 作者配置与 Native 编译支持精确 text.rich 字段,避免借用其他图片字段授权。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用具名动作编辑富文本或需要后台管理通知投递的 V2 应用。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"升级工具链;富文本插图依赖对应平台编译支持,开发态已有记录上传需平台开发态附件 RLS 修复。",
|
|
18
|
+
"通知死信 messageId 过滤和来源关联需对应平台版本;管理员分别授予 read、content:read、delivery:retry 权限。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"投影阶段尚无消息时死信关联字段为空;已解决死信保持既有 not-found 响应,客户端应刷新状态。",
|
|
22
|
+
"SDK 和平台源码验证不代替目标应用实际图片上传、通知投递及权限验收。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "新增富文本声明和通知来源过滤需同步支持本次变更的平台;不扩大普通用户发送权限。",
|
|
29
|
+
"v1": "独立 V1 引擎不受影响。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "e30dad108c478ee6cce5a1632cbd620cbf650999c9d2fd39973482c2edb01ad9",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.8"
|
|
33
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.31.9",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.31.9:审批凭据绑定与附件预览修复",
|
|
6
|
+
"summary": "修复登录面刷新后既有审批凭据失配,以及流程附件预览遗漏 CSRF 请求头的问题。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"工作流操作保留签发详情时的 CSRF 绑定,登录面刷新不会将已签发操作错误地改用新凭据。",
|
|
10
|
+
"流程附件元数据、封面缩略图与文件内容通过 SDK 携带所需请求头,保留实例和字段授权。",
|
|
11
|
+
"审批确认弹窗持续展示操作失败提示,便于用户了解未完成状态。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用任务或实例审批、流程附件预览的 V2 应用。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"升级 openxiangda 至 2.31.9 并重新构建应用,CLI 同批次更新模板依赖。",
|
|
18
|
+
"发布后核对真实审批提交、业务状态回读和封面预览;不需要修改角色权限或数据库。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"网络结果不明的写操作不会自动重试,应先查询原操作状态。",
|
|
22
|
+
"原始文件 URL 仍不代替带授权头的 SDK 文件预览,HTML 等附件的服务端隔离策略保持不变。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "沿用既有工作流 Surface、一次性命令凭据与文件授权契约,无服务端放宽。",
|
|
29
|
+
"v1": "独立 V1 引擎不受影响。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "451b5b993046436de85f8f1aefd3acdad4677efe5754969d0adb5c6c8a9758b1",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.31.9"
|
|
33
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.32.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.32.0:自定义后台壳层与精确时间交互",
|
|
6
|
+
"summary": "提供正式后台壳层扩展,改进时间禁选、业务错误与内网开发诊断。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"应用可通过 ui.admin 提供完整后台壳层或顶栏、侧栏、页脚插槽,消费权限过滤后的导航与身份。",
|
|
9
|
+
"消息与待办导航可分别配置显示,资源深链接与移动端页面统一使用自定义壳层。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"日期时间控件按时区精确禁用小时、分钟、秒,保留输入校验和受控值。",
|
|
13
|
+
"业务拒绝的中文 message 与错误码、requestId 分离,避免页面丢失实际提示。",
|
|
14
|
+
"开发连接故障区分 DNS、TCP、TLS 与超时并提供安全恢复提示。"
|
|
15
|
+
],
|
|
16
|
+
"affectedUsers": [
|
|
17
|
+
"使用自定义管理后台、精确日期范围或校内网络开发的 V2 应用。"
|
|
18
|
+
],
|
|
19
|
+
"upgradeSteps": [
|
|
20
|
+
"升级 openxiangda 至 2.32.0,重新安装依赖并构建应用。CLI 模板随同版本化。",
|
|
21
|
+
"按公开 ui.admin 契约接入壳层;路由、登录与授权继续由平台负责。",
|
|
22
|
+
"基础记录字段默认读取及受管下载文件名需要配套平台后端升级;仅升级 npm 不会更改服务端。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"自定义壳层接入和业务页面设计仍由应用负责,升级 SDK 不自动替换现有 UI。",
|
|
26
|
+
"网络诊断不自动改变 VPN、系统代理、证书或重试未知结果写请求。",
|
|
27
|
+
"前端时间禁选不能替代应用服务端业务时间守卫。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"workspaceGenerations": "v2",
|
|
33
|
+
"platform": "沿用现有认证、权限与路由协议;基础记录元数据的后端调整需对应站点发布。",
|
|
34
|
+
"v1": "V1 引擎与既有业务不受本次 SDK 改动影响。"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "987351f0bde76980d80f2a1ea8741c7e4697ef7b659ca679f5bf9b2797c8e8b2",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.32.0"
|
|
38
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.33.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.33.0:事务构建与部署前置诊断",
|
|
6
|
+
"summary": "在提交前定位事务组合错误,在构建前发现平台依赖故障。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"openxiangda/nest 提供 createDataTransaction、diagnoseDataTransaction 和结构化构建错误。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"支持平台实时前置检查,发现内核、源码托管及镜像仓故障时停止后续构建。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"编写后端事务或向私有平台部署应用的 V2 开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"升级 openxiangda 到 2.33.0 并重新安装依赖。",
|
|
18
|
+
"平台部署对应后端后自动启用前置诊断;事务构建器按文档显式接入。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"只读预检不保证后续写入或容量;原有部署和权限检查继续执行。",
|
|
22
|
+
"事务构建不自动合并重复写入,不替代服务端权限和并发判断。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "前置检查按平台 capability 启用,旧站保持原部署流程。",
|
|
29
|
+
"v1": "V1 引擎与业务不变。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "6738fcde83daed062691a30f4c4161d5f59b8024303ba2c4c7fd377c6886de70",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.33.0"
|
|
33
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.0:持久排队业务计划与结果恢复",
|
|
6
|
+
"summary": "新增由平台持久受理并自动处理的业务命令,支持关闭页面后继续执行与本人跨设备恢复。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"新增 durable 受管命令、独立能力门禁、有界参数及生成的 backend-plan handler 清单。",
|
|
9
|
+
"openxiangda/nest 提供受执行证明约束的只读计划 handler,平台负责最终原子提交。",
|
|
10
|
+
"openxiangda/react 与 mobile 提供 useDurableCommand,支持显式提交、原键恢复、本人结果和退避轮询。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"严格区分内置 permit 配额所有权与应用 durable 计划,普通业务模型无需迁移到命令独占所有权。",
|
|
14
|
+
"执行上下文拒绝普通 SDK 写入、事务、通知和 OAuth,读取响应验证标准记录结构。"
|
|
15
|
+
],
|
|
16
|
+
"affectedUsers": [
|
|
17
|
+
"构建活动报名、预约、抢票及其他需要持久排队事务的 V2 应用开发者。"
|
|
18
|
+
],
|
|
19
|
+
"upgradeSteps": [
|
|
20
|
+
"升级 openxiangda 到 2.34.0,重新安装依赖并生成应用契约。",
|
|
21
|
+
"先部署支持 data.managed-concurrency.durable@1.0.0 的平台,再声明 durable 命令、handler manifest 和前端恢复流程。",
|
|
22
|
+
"在隔离测试数据上验证关闭浏览器、原请求恢复、取消后重报和业务原子结果,再分级测量实际容量。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"应用只返回受声明约束的事务计划,不能在 handler 内发送通知或调用普通写入接口。",
|
|
26
|
+
"受理成功不等于业务成功;队列位置为近似投影,不能推导精确等待时间或服务器容量。",
|
|
27
|
+
"旧 permit 模式保留,未升级平台会拒绝 durable 包;回滚前须停止新受理并核对已有请求。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"workspaceGenerations": "v2",
|
|
33
|
+
"platform": "durable 必须具备 data.managed-concurrency.durable@1.0.0,旧 permit 契约继续支持。",
|
|
34
|
+
"v1": "V1 引擎与业务不变。"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "929abb0ea8cdbb32e38c39131540cd64a248c4e1a68dbde9ff187f35438f8da0",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.0"
|
|
38
|
+
}
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.1:持久申请受理恢复预算",
|
|
6
|
+
"summary": "支持配置最长30分钟的自动受理恢复,并保留首次明确提交时间和原申请编号。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"useDurableCommand 可用 acceptanceRecoveryMs 配置120秒至30分钟的受理恢复预算。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"刷新及恢复原申请不再重新计算受理重试预算;截止后保留查询和迟到结果恢复能力。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"需要较长排队等待的活动报名、预约和抢票应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"升级 openxiangda 到2.34.1,在需要长时间恢复的业务明确配置 acceptanceRecoveryMs。",
|
|
18
|
+
"验证原键恢复、截止后查询、未知应答及目标环境的完整排队容量。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"默认受理恢复预算仍为120秒;配置值是客户端自动入队预算,不是服务端最终完成承诺。",
|
|
22
|
+
"旧意图没有首次时间时,只能从首次明确恢复计时,无法证明历史发起时间。",
|
|
23
|
+
"受理成功不等于报名成功;实际容量需使用独立用户在目标环境验证。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"workspaceGenerations": "v2",
|
|
29
|
+
"platform": "沿用 data.managed-concurrency.durable@1.0.0;不改变平台事实和permit协议。",
|
|
30
|
+
"v1": "V1引擎及业务不变。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "f7297f5c779f079b48aa95ef594c9b4d7c373207467e1410aacfda57ca361451",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.1"
|
|
34
|
+
}
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.2:受管读取繁忙恢复与原申请观察期限",
|
|
6
|
+
"summary": "为受管只读查询提供有界退避,并使持久申请观察遵守原始三十分钟期限,真实依赖和权限故障立即显露。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"受管详情、本人申请、命令结果和配额查询默认最多恢复120秒、12次请求,可通过budgetMs或AbortSignal收窄。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"读取恢复冻结原参数及身份,遵循服务端Retry-After,只重试明确的容量繁忙;写请求保持单次发送。",
|
|
12
|
+
"已受理申请以原首次提交时间观察,跨设备使用原acceptedAt;刷新不会延长期限,超期后保留原编号用于显式查询。",
|
|
13
|
+
"持久结果轮询不再吞掉真实网络、依赖和权限故障。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"使用受管读取和持久排队能力的活动报名、预约及抢票应用开发者。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"将应用openxiangda精确依赖升级到2.34.2,刷新同版本资料后检查并部署测试环境。",
|
|
20
|
+
"验证繁忙恢复、故障提示、原键跨设备恢复及三十分钟期限;在目标硬件测量完整混合负载。"
|
|
21
|
+
],
|
|
22
|
+
"knownLimitations": [
|
|
23
|
+
"读取恢复仅覆盖明确只读方法;普通Data API和写入没有新增自动重试。",
|
|
24
|
+
"默认受理恢复预算仍为120秒,accepted观察最长三十分钟;客户端预算不承诺服务端完成时间。",
|
|
25
|
+
"自动观察停止后可能存在迟到结果,应查询原申请;容量仍需目标环境实测。"
|
|
26
|
+
],
|
|
27
|
+
"issues": [],
|
|
28
|
+
"compatibility": {
|
|
29
|
+
"node": ">=24",
|
|
30
|
+
"workspaceGenerations": "v2",
|
|
31
|
+
"platform": "沿用data.managed-concurrency.durable@1.0.0,兼容已知API_BUSY/RESULT_BUSY的旧503;新入口预算429需匹配平台版本。",
|
|
32
|
+
"v1": "V1引擎及业务不变。"
|
|
33
|
+
},
|
|
34
|
+
"sha256": "93594d8cc407bef730868e32737ba3e78ca5df955e2d33bc0bb3f6eec8f1d1f9",
|
|
35
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.2"
|
|
36
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.3:显式长期只读繁忙恢复",
|
|
6
|
+
"summary": "允许热点详情等只读页面显式选择最长三十分钟恢复;默认两分钟策略及持久申请原期限保持,取消与真实故障仍及时结束。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"受管read、mine、result、allocation可显式设置budgetMs,超过120秒时最多恢复30分钟、120次请求;默认120秒和12次保持。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"长期读取仍冻结原输入、身份与权限视角,按原调用截止及Retry-After/抖动退避;AbortSignal中止请求和等待。",
|
|
12
|
+
"持久申请控制器显式保留原单次120秒上限,防止SDK扩展隐式改变既有受理和观察行为。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"使用受管热点详情和持久排队能力的活动报名、预约及抢票应用开发者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"将应用openxiangda精确升级到2.34.3并刷新资料;应用按业务选择显式预算、离页取消及未结束窗口的固定截止。",
|
|
19
|
+
"验证繁忙恢复、真实网络/权限/依赖错误、身份切换和持久申请原期限后部署测试环境,目标硬件容量另外实测。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"仅已知只读繁忙恢复;不吞未知429、网络、权限或依赖失败,不自动重试写入。",
|
|
23
|
+
"客户端等待窗口不承诺服务端容量或最终处理时间,不代表已经受理或报名。",
|
|
24
|
+
"长期恢复不自动启用,普通Data API、平台后端与V1业务不变;刷新固定窗口由应用生命周期接入。"
|
|
25
|
+
],
|
|
26
|
+
"issues": [],
|
|
27
|
+
"compatibility": {
|
|
28
|
+
"node": ">=24",
|
|
29
|
+
"workspaceGenerations": "v2",
|
|
30
|
+
"platform": "沿用data.managed-concurrency.durable@1.0.0;新入口429预算错误需要匹配平台版本。",
|
|
31
|
+
"v1": "V1引擎及业务不变。"
|
|
32
|
+
},
|
|
33
|
+
"sha256": "fe3ba4a4c33af0e158cbe5bb7b25c9ba4c75e4ef97a02479eded9c71885d00ec",
|
|
34
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.3"
|
|
35
|
+
}
|