openxiangda 2.34.2 → 2.35.3

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.
Files changed (162) hide show
  1. package/dist/browser/application.d.ts.map +1 -1
  2. package/dist/browser/application.js +5 -4
  3. package/dist/browser/application.js.map +1 -1
  4. package/dist/browser/components/resource/useResourceFormDrafts.d.ts.map +1 -1
  5. package/dist/browser/components/workflow/StandardWorkflowPages.d.ts +6 -2
  6. package/dist/browser/components/workflow/StandardWorkflowPages.d.ts.map +1 -1
  7. package/dist/browser/components/workflow/StandardWorkflowPages.js +6 -6
  8. package/dist/browser/components/workflow/StandardWorkflowPages.js.map +1 -1
  9. package/dist/browser/components/workflow/WorkflowDiagram.d.ts +16 -0
  10. package/dist/browser/components/workflow/WorkflowDiagram.d.ts.map +1 -0
  11. package/dist/browser/components/workflow/WorkflowDiagram.js +110 -0
  12. package/dist/browser/components/workflow/WorkflowDiagram.js.map +1 -0
  13. package/dist/browser/components/workflow/WorkflowFlowCanvas.d.ts +23 -0
  14. package/dist/browser/components/workflow/WorkflowFlowCanvas.d.ts.map +1 -0
  15. package/dist/browser/components/workflow/WorkflowFlowCanvas.js +78 -0
  16. package/dist/browser/components/workflow/WorkflowFlowCanvas.js.map +1 -0
  17. package/dist/browser/components/workflow/WorkflowNodeCard.d.ts +15 -0
  18. package/dist/browser/components/workflow/WorkflowNodeCard.d.ts.map +1 -0
  19. package/dist/browser/components/workflow/WorkflowNodeCard.js +13 -0
  20. package/dist/browser/components/workflow/WorkflowNodeCard.js.map +1 -0
  21. package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.d.ts +13 -0
  22. package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.d.ts.map +1 -0
  23. package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.js +150 -0
  24. package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.js.map +1 -0
  25. package/dist/browser/components/workflow/workflow-flow-layout.d.ts +28 -0
  26. package/dist/browser/components/workflow/workflow-flow-layout.d.ts.map +1 -0
  27. package/dist/browser/components/workflow/workflow-flow-layout.js +54 -0
  28. package/dist/browser/components/workflow/workflow-flow-layout.js.map +1 -0
  29. package/dist/browser/durable-command.d.ts.map +1 -1
  30. package/dist/browser/durable-command.js +4 -2
  31. package/dist/browser/durable-command.js.map +1 -1
  32. package/dist/browser/managed-command.d.ts +5 -1
  33. package/dist/browser/managed-command.d.ts.map +1 -1
  34. package/dist/browser/managed-command.js.map +1 -1
  35. package/dist/browser/managed-read-recovery.d.ts.map +1 -1
  36. package/dist/browser/managed-read-recovery.js +8 -5
  37. package/dist/browser/managed-read-recovery.js.map +1 -1
  38. package/dist/browser/platform-client.d.ts +9 -0
  39. package/dist/browser/platform-client.d.ts.map +1 -1
  40. package/dist/browser/platform-client.js +157 -42
  41. package/dist/browser/platform-client.js.map +1 -1
  42. package/dist/browser/runtime-authorization-recovery.d.ts +7 -0
  43. package/dist/browser/runtime-authorization-recovery.d.ts.map +1 -0
  44. package/dist/browser/runtime-authorization-recovery.js +119 -0
  45. package/dist/browser/runtime-authorization-recovery.js.map +1 -0
  46. package/dist/browser/runtime.d.ts.map +1 -1
  47. package/dist/browser/runtime.js +34 -12
  48. package/dist/browser/runtime.js.map +1 -1
  49. package/dist/browser/styles.css +74 -0
  50. package/dist/core.d.ts +4 -0
  51. package/dist/core.d.ts.map +1 -1
  52. package/dist/core.js +2 -0
  53. package/dist/core.js.map +1 -1
  54. package/dist/react.d.ts +2 -0
  55. package/dist/react.d.ts.map +1 -1
  56. package/dist/react.js +2 -0
  57. package/dist/react.js.map +1 -1
  58. package/documentation/administration.md +63 -0
  59. package/documentation/getting-started.md +7 -7
  60. package/documentation/managed-concurrency-frontend.md +8 -3
  61. package/documentation/managed-concurrency.md +10 -0
  62. package/documentation/manifest.json +6 -6
  63. package/documentation/workflow-events.md +24 -0
  64. package/package.json +36 -24
  65. package/releases/2.35.0.json +42 -0
  66. package/releases/2.35.1.json +43 -0
  67. package/releases/2.35.2.json +45 -0
  68. package/releases/2.35.3.json +46 -0
  69. package/skills/manifest.json +1 -1
  70. package/skills/openxiangda-v2/SKILL.md +4 -4
  71. package/skills/openxiangda-v2/references/administration.md +63 -0
  72. package/skills/openxiangda-v2/references/getting-started.md +7 -7
  73. package/skills/openxiangda-v2/references/managed-concurrency-frontend.md +8 -3
  74. package/skills/openxiangda-v2/references/managed-concurrency.md +10 -0
  75. package/skills/openxiangda-v2/references/workflow-events.md +24 -0
  76. package/releases/2.0.0.json +0 -50
  77. package/releases/2.0.1.json +0 -39
  78. package/releases/2.1.0.json +0 -44
  79. package/releases/2.1.1.json +0 -48
  80. package/releases/2.10.0.json +0 -42
  81. package/releases/2.11.0.json +0 -41
  82. package/releases/2.12.0.json +0 -38
  83. package/releases/2.13.0.json +0 -41
  84. package/releases/2.13.1.json +0 -33
  85. package/releases/2.13.2.json +0 -31
  86. package/releases/2.14.0.json +0 -41
  87. package/releases/2.15.0.json +0 -40
  88. package/releases/2.16.0.json +0 -41
  89. package/releases/2.17.0.json +0 -39
  90. package/releases/2.17.1.json +0 -34
  91. package/releases/2.18.0.json +0 -37
  92. package/releases/2.18.1.json +0 -31
  93. package/releases/2.18.10.json +0 -29
  94. package/releases/2.18.2.json +0 -30
  95. package/releases/2.18.3.json +0 -30
  96. package/releases/2.18.9.json +0 -37
  97. package/releases/2.19.0.json +0 -38
  98. package/releases/2.2.0.json +0 -48
  99. package/releases/2.2.1.json +0 -35
  100. package/releases/2.2.2.json +0 -34
  101. package/releases/2.20.0.json +0 -36
  102. package/releases/2.20.1.json +0 -30
  103. package/releases/2.20.4.json +0 -30
  104. package/releases/2.21.0.json +0 -35
  105. package/releases/2.21.1.json +0 -36
  106. package/releases/2.21.2.json +0 -34
  107. package/releases/2.21.3.json +0 -31
  108. package/releases/2.21.4.json +0 -31
  109. package/releases/2.22.0.json +0 -35
  110. package/releases/2.22.1.json +0 -32
  111. package/releases/2.22.2.json +0 -35
  112. package/releases/2.22.3.json +0 -32
  113. package/releases/2.22.4.json +0 -33
  114. package/releases/2.22.5.json +0 -31
  115. package/releases/2.22.6.json +0 -29
  116. package/releases/2.22.7.json +0 -29
  117. package/releases/2.23.0.json +0 -34
  118. package/releases/2.24.0.json +0 -33
  119. package/releases/2.24.1.json +0 -33
  120. package/releases/2.24.2.json +0 -31
  121. package/releases/2.24.3.json +0 -33
  122. package/releases/2.25.0.json +0 -31
  123. package/releases/2.25.1.json +0 -33
  124. package/releases/2.25.2.json +0 -32
  125. package/releases/2.25.3.json +0 -32
  126. package/releases/2.26.0.json +0 -41
  127. package/releases/2.27.0.json +0 -38
  128. package/releases/2.28.0.json +0 -37
  129. package/releases/2.28.1.json +0 -34
  130. package/releases/2.29.0.json +0 -37
  131. package/releases/2.29.1.json +0 -34
  132. package/releases/2.29.2.json +0 -32
  133. package/releases/2.3.0.json +0 -37
  134. package/releases/2.30.0.json +0 -34
  135. package/releases/2.31.0.json +0 -39
  136. package/releases/2.31.1.json +0 -38
  137. package/releases/2.31.2.json +0 -34
  138. package/releases/2.31.3.json +0 -32
  139. package/releases/2.31.4.json +0 -33
  140. package/releases/2.31.5.json +0 -33
  141. package/releases/2.31.6.json +0 -29
  142. package/releases/2.31.7.json +0 -29
  143. package/releases/2.31.8.json +0 -33
  144. package/releases/2.31.9.json +0 -33
  145. package/releases/2.32.0.json +0 -38
  146. package/releases/2.33.0.json +0 -33
  147. package/releases/2.34.0.json +0 -38
  148. package/releases/2.34.1.json +0 -34
  149. package/releases/2.34.2.json +0 -36
  150. package/releases/2.4.0.json +0 -37
  151. package/releases/2.4.1.json +0 -35
  152. package/releases/2.5.0.json +0 -37
  153. package/releases/2.6.0.json +0 -37
  154. package/releases/2.7.0.json +0 -37
  155. package/releases/2.7.1.json +0 -31
  156. package/releases/2.8.0.json +0 -32
  157. package/releases/2.8.1.json +0 -30
  158. package/releases/2.9.0.json +0 -33
  159. package/releases/2.9.1.json +0 -31
  160. package/releases/2.9.2.json +0 -33
  161. package/releases/2.9.3.json +0 -31
  162. package/releases/2.9.4.json +0 -37
@@ -1,34 +0,0 @@
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
- }
@@ -1,32 +0,0 @@
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
- }
@@ -1,33 +0,0 @@
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
- }
@@ -1,33 +0,0 @@
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
- }
@@ -1,29 +0,0 @@
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
- }
@@ -1,29 +0,0 @@
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
- }
@@ -1,33 +0,0 @@
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
- }
@@ -1,33 +0,0 @@
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
- }
@@ -1,38 +0,0 @@
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
- }
@@ -1,33 +0,0 @@
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
- }
@@ -1,38 +0,0 @@
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
- }
@@ -1,34 +0,0 @@
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
- }
@@ -1,36 +0,0 @@
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
- }
@@ -1,37 +0,0 @@
1
- {
2
- "schemaVersion": "openxiangda.release-notes/v1",
3
- "version": "2.4.0",
4
- "title": "事务接受时刻与预约时间窗口",
5
- "status": "reviewed",
6
- "summary": "增加绑定提交字段的时间守卫,统一在锁等待结束后使用平台数据库时间判断业务期限。",
7
- "newFeatures": [
8
- "operation-time 守卫可检查 create/update 中的 datetime 字段,支持正负 366 天以内的整数毫秒偏移和六种比较。"
9
- ],
10
- "fixes": [
11
- "动态时间条件使用守卫锁及写入前校验完成后的数据库接受时刻,成功重放保持原 evaluatedAt。"
12
- ],
13
- "affectedUsers": [
14
- "需要预约窗口、截止时间、签到时间或并发事务时间条件的 V2 应用开发者。"
15
- ],
16
- "compatibility": {
17
- "node": ">=24",
18
- "workspaceGenerations": [
19
- "v1",
20
- "v2"
21
- ],
22
- "v1Policy": "V1 引擎和已有应用契约不变。",
23
- "platformPolicy": "新编译的数据应用要求 Data API 1.1.0 和匹配的共享校验器;平台预检拒绝不支持该能力的目标。"
24
- },
25
- "upgradeSteps": [
26
- "将应用精确依赖升级至 openxiangda 2.4.0,更新锁文件并刷新技能资料。",
27
- "平台部署匹配版本后执行正式检查、测试发布、数据库截止和真实角色验收。"
28
- ],
29
- "knownLimitations": [
30
- "evaluatedAt 是动态条件的接受时刻,不是最终数据库提交时刻。",
31
- "字段必须是声明且可写的 datetime 字面值,不支持空值、嵌套路径或操作引用。",
32
- "工具包发布不代表平台已部署或应用业务验收已通过。"
33
- ],
34
- "issues": [],
35
- "sha256": "2c4e0bf9f880e72a454010d2590fe3ac5b2993a215473c8e29ef29e77431e42a",
36
- "url": "https://github.com/1377385356/openxiangda/releases/tag/v2.4.0"
37
- }
@@ -1,35 +0,0 @@
1
- {
2
- "schemaVersion": "openxiangda.release-notes/v1",
3
- "version": "2.4.1",
4
- "title": "事件处理器依赖作用域修复",
5
- "status": "reviewed",
6
- "summary": "事件处理器可正常注入请求级通知服务,签名与回执校验后再由所属 Nest 模块解析依赖。",
7
- "newFeatures": [],
8
- "fixes": [
9
- "修复请求级依赖使事件处理器构造函数未执行、handle 调用失败的问题。",
10
- "同名 provider 严格按所属模块解析,并发投递与失败重试使用独立作用域;静态单例继续复用。"
11
- ],
12
- "affectedUsers": [
13
- "使用 Nest 签名事件处理器及请求级通知服务或瞬态依赖的 V2 应用开发者。"
14
- ],
15
- "compatibility": {
16
- "node": ">=24",
17
- "workspaceGenerations": [
18
- "v1",
19
- "v2"
20
- ],
21
- "v1Policy": "V1 引擎与已有应用契约不变。",
22
- "platformPolicy": "沿用 2.4.0 的 Data API 1.1.0 要求;事件签名、回执、身份与部署协议不变。"
23
- },
24
- "upgradeSteps": [
25
- "将应用精确依赖升级至 openxiangda 2.4.1,刷新工作区资料并重新检查。",
26
- "重新发布应用后验证真实事件、通知送达、重复投递与失败恢复。"
27
- ],
28
- "knownLimitations": [
29
- "事件作用域的 REQUEST 不含用户授权,sendFromEvent 仅在已验证的事件执行期间可用。",
30
- "SDK 测试通过不代表真实平台通知送达或应用业务验收已完成。"
31
- ],
32
- "issues": [],
33
- "sha256": "f81f626e3fb91069c4f5d94da48a80400ae3fca5e3b55ab0d77e0a7c82dc7681",
34
- "url": "https://github.com/1377385356/openxiangda/releases/tag/v2.4.1"
35
- }
@@ -1,37 +0,0 @@
1
- {
2
- "schemaVersion": "openxiangda.release-notes/v1",
3
- "version": "2.5.0",
4
- "title": "按业务记录恢复原流程命令",
5
- "status": "reviewed",
6
- "summary": "浏览器和 Nest 可在重新进入详情时按业务记录查找原流程命令,继续原回执和进度查询。",
7
- "newFeatures": [
8
- "增加当前用户范围的流程命令分页查询,支持精确记录、流程和操作筛选,每页最多 50 条。"
9
- ],
10
- "fixes": [
11
- "补齐业务记录已提交但流程事件尚未投影时,从列表重新进入详情无法定位原命令的恢复路径。"
12
- ],
13
- "affectedUsers": [
14
- "使用 Business Process 原子提交业务数据与流程的 V2 应用开发者。"
15
- ],
16
- "compatibility": {
17
- "node": ">=24",
18
- "workspaceGenerations": [
19
- "v1",
20
- "v2"
21
- ],
22
- "v1Policy": "V1 引擎和已有应用不变。",
23
- "platformPolicy": "使用 Business Process 的新编译包要求 durable-command 1.1.0 和匹配的共享校验器;旧客户端继续兼容。"
24
- },
25
- "upgradeSteps": [
26
- "将应用精确依赖升级至 openxiangda 2.5.0,更新锁文件并刷新技能资料。",
27
- "平台部署匹配版本后执行检查和测试发布,验证重新进入详情时恢复原命令而不重复提交。"
28
- ],
29
- "knownLimitations": [
30
- "查询沿用原命令的发起人或既有超级管理员权限,记录读取权限不授予他人命令访问。",
31
- "同一记录可能有多次流程,应用须根据业务约束选择原命令,不能任意选择第一条。",
32
- "包发布、平台部署和实际业务验收分别验证。"
33
- ],
34
- "issues": [],
35
- "sha256": "35a3bd6f8f97d3261243e1c65e2876a946448c5af455f43ababf18bd8f6f3653",
36
- "url": "https://github.com/1377385356/openxiangda/releases/tag/v2.5.0"
37
- }
@@ -1,37 +0,0 @@
1
- {
2
- "schemaVersion": "openxiangda.release-notes/v1",
3
- "version": "2.6.0",
4
- "title": "统一应用时区与日期时间输入",
5
- "status": "reviewed",
6
- "summary": "应用可指定业务展示时区,标准字段、审批详情、待办、通知和审计时间统一显示,日期时间输入仍保存 UTC。",
7
- "newFeatures": [
8
- "OpenXiangdaApplication 和 OpenXiangdaUiProvider 接受可选 timeZone;日期时间字段可覆盖时区并声明 min、max 和 minuteStep。"
9
- ],
10
- "fixes": [
11
- "修复设备时区不同导致日期时间编辑和公共详情、中心时间不一致的问题,拒绝夏令时不存在或重复的本地时间。"
12
- ],
13
- "affectedUsers": [
14
- "需要固定业务时区或限制日期时间输入的 V2 应用开发者。"
15
- ],
16
- "compatibility": {
17
- "node": ">=24",
18
- "workspaceGenerations": [
19
- "v1",
20
- "v2"
21
- ],
22
- "v1Policy": "V1 引擎和已有应用不变。",
23
- "platformPolicy": "展示与输入能力,无新增服务端契约或数据库迁移。未配置时区和限制的应用保留设备本地行为。"
24
- },
25
- "upgradeSteps": [
26
- "将应用精确依赖升级至 openxiangda 2.6.0,更新锁文件并刷新技能资料。",
27
- "在应用入口指定业务 timeZone,验证 PC 和移动端编辑、审批摘要与各中心显示。"
28
- ],
29
- "knownLimitations": [
30
- "时区只影响呈现;服务端仍须独立验证业务时间窗口和授权。",
31
- "手机指定时区的日期时间滚轮提供当前选择前后各 365 天并按限制收窄;夏令时重复时间需选择其他无歧义时间。",
32
- "包发布、应用部署和实际业务验收分别验证。"
33
- ],
34
- "issues": [],
35
- "sha256": "ba11ac3a69cbd9dd27e339c1d84642af99e107ca1170f0876b8be0583abda79f",
36
- "url": "https://github.com/1377385356/openxiangda/releases/tag/v2.6.0"
37
- }
@@ -1,37 +0,0 @@
1
- {
2
- "schemaVersion": "openxiangda.release-notes/v1",
3
- "version": "2.7.0",
4
- "title": "应用统一保护未保存内容",
5
- "status": "reviewed",
6
- "summary": "自定义表单可注册未保存状态,应用统一处理站内跳转、浏览器历史和刷新关闭提示。",
7
- "newFeatures": [
8
- "增加 useUnsavedChangesGuard,聚合多个表单的未保存状态,取消导航保留输入和原位置,提交成功后解除保护。"
9
- ],
10
- "fixes": [
11
- "补齐原 BrowserRouter 无法使用标准 useBlocker 导致自定义表单浏览器前进后退未受保护的问题。"
12
- ],
13
- "affectedUsers": [
14
- "有自定义录入页面、异步提交或未知结果恢复的 V2 应用开发者。"
15
- ],
16
- "compatibility": {
17
- "node": ">=24",
18
- "workspaceGenerations": [
19
- "v1",
20
- "v2"
21
- ],
22
- "v1Policy": "V1 引擎和已有应用不变。",
23
- "platformPolicy": "公共 React 路由生命周期调整,无服务端契约或数据库变更;应用仍使用既有 Routes、Link 和 navigate。"
24
- },
25
- "upgradeSteps": [
26
- "精确升级到 openxiangda 2.7.0 并刷新技能资料。",
27
- "在应用入口内使用 useUnsavedChangesGuard,涵盖未保存内容和结果未知状态,验证成功后解除以及取消后的输入保留。"
28
- ],
29
- "knownLimitations": [
30
- "原生刷新/关闭提示受浏览器限制,不能自定义提示文字。",
31
- "该能力不持久化草稿或代替原提交回执恢复;应用不得直接操作 history.pushState。",
32
- "包发布、应用部署与真实业务验收分别验证。"
33
- ],
34
- "issues": [],
35
- "sha256": "e8af0fc7c484cad1dc59ce982432e6a2fd4451d7f455141edc2d6128a057542e",
36
- "url": "https://github.com/1377385356/openxiangda/releases/tag/v2.7.0"
37
- }