openxiangda 2.34.3 → 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.
- package/dist/browser/application.d.ts.map +1 -1
- package/dist/browser/application.js +5 -4
- package/dist/browser/application.js.map +1 -1
- package/dist/browser/components/resource/useResourceFormDrafts.d.ts.map +1 -1
- package/dist/browser/components/workflow/StandardWorkflowPages.d.ts +6 -2
- package/dist/browser/components/workflow/StandardWorkflowPages.d.ts.map +1 -1
- package/dist/browser/components/workflow/StandardWorkflowPages.js +6 -6
- package/dist/browser/components/workflow/StandardWorkflowPages.js.map +1 -1
- package/dist/browser/components/workflow/WorkflowDiagram.d.ts +16 -0
- package/dist/browser/components/workflow/WorkflowDiagram.d.ts.map +1 -0
- package/dist/browser/components/workflow/WorkflowDiagram.js +110 -0
- package/dist/browser/components/workflow/WorkflowDiagram.js.map +1 -0
- package/dist/browser/components/workflow/WorkflowFlowCanvas.d.ts +23 -0
- package/dist/browser/components/workflow/WorkflowFlowCanvas.d.ts.map +1 -0
- package/dist/browser/components/workflow/WorkflowFlowCanvas.js +78 -0
- package/dist/browser/components/workflow/WorkflowFlowCanvas.js.map +1 -0
- package/dist/browser/components/workflow/WorkflowNodeCard.d.ts +15 -0
- package/dist/browser/components/workflow/WorkflowNodeCard.d.ts.map +1 -0
- package/dist/browser/components/workflow/WorkflowNodeCard.js +13 -0
- package/dist/browser/components/workflow/WorkflowNodeCard.js.map +1 -0
- package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.d.ts +13 -0
- package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.d.ts.map +1 -0
- package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.js +150 -0
- package/dist/browser/components/workflow/WorkflowNodeConfigurationEditor.js.map +1 -0
- package/dist/browser/components/workflow/workflow-flow-layout.d.ts +28 -0
- package/dist/browser/components/workflow/workflow-flow-layout.d.ts.map +1 -0
- package/dist/browser/components/workflow/workflow-flow-layout.js +54 -0
- package/dist/browser/components/workflow/workflow-flow-layout.js.map +1 -0
- package/dist/browser/platform-client.d.ts +9 -0
- package/dist/browser/platform-client.d.ts.map +1 -1
- package/dist/browser/platform-client.js +157 -42
- package/dist/browser/platform-client.js.map +1 -1
- package/dist/browser/runtime-authorization-recovery.d.ts +7 -0
- package/dist/browser/runtime-authorization-recovery.d.ts.map +1 -0
- package/dist/browser/runtime-authorization-recovery.js +119 -0
- package/dist/browser/runtime-authorization-recovery.js.map +1 -0
- package/dist/browser/runtime.d.ts.map +1 -1
- package/dist/browser/runtime.js +34 -12
- package/dist/browser/runtime.js.map +1 -1
- package/dist/browser/styles.css +74 -0
- package/dist/core.d.ts +4 -0
- package/dist/core.d.ts.map +1 -1
- package/dist/core.js +2 -0
- package/dist/core.js.map +1 -1
- package/dist/react.d.ts +2 -0
- package/dist/react.d.ts.map +1 -1
- package/dist/react.js +2 -0
- package/dist/react.js.map +1 -1
- package/documentation/administration.md +63 -0
- package/documentation/getting-started.md +7 -7
- package/documentation/managed-concurrency.md +10 -0
- package/documentation/manifest.json +5 -5
- package/documentation/workflow-events.md +24 -0
- package/package.json +36 -23
- 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/skills/manifest.json +1 -1
- package/skills/openxiangda-v2/SKILL.md +4 -4
- package/skills/openxiangda-v2/references/administration.md +63 -0
- package/skills/openxiangda-v2/references/getting-started.md +7 -7
- package/skills/openxiangda-v2/references/managed-concurrency.md +10 -0
- package/skills/openxiangda-v2/references/workflow-events.md +24 -0
- package/releases/2.0.0.json +0 -50
- package/releases/2.0.1.json +0 -39
- package/releases/2.1.0.json +0 -44
- package/releases/2.1.1.json +0 -48
- package/releases/2.10.0.json +0 -42
- package/releases/2.11.0.json +0 -41
- package/releases/2.12.0.json +0 -38
- package/releases/2.13.0.json +0 -41
- package/releases/2.13.1.json +0 -33
- package/releases/2.13.2.json +0 -31
- package/releases/2.14.0.json +0 -41
- package/releases/2.15.0.json +0 -40
- package/releases/2.16.0.json +0 -41
- package/releases/2.17.0.json +0 -39
- package/releases/2.17.1.json +0 -34
- package/releases/2.18.0.json +0 -37
- package/releases/2.18.1.json +0 -31
- package/releases/2.18.10.json +0 -29
- package/releases/2.18.2.json +0 -30
- package/releases/2.18.3.json +0 -30
- package/releases/2.18.9.json +0 -37
- package/releases/2.19.0.json +0 -38
- package/releases/2.2.0.json +0 -48
- package/releases/2.2.1.json +0 -35
- package/releases/2.2.2.json +0 -34
- package/releases/2.20.0.json +0 -36
- package/releases/2.20.1.json +0 -30
- package/releases/2.20.4.json +0 -30
- package/releases/2.21.0.json +0 -35
- package/releases/2.21.1.json +0 -36
- package/releases/2.21.2.json +0 -34
- package/releases/2.21.3.json +0 -31
- package/releases/2.21.4.json +0 -31
- package/releases/2.22.0.json +0 -35
- package/releases/2.22.1.json +0 -32
- package/releases/2.22.2.json +0 -35
- package/releases/2.22.3.json +0 -32
- package/releases/2.22.4.json +0 -33
- package/releases/2.22.5.json +0 -31
- package/releases/2.22.6.json +0 -29
- package/releases/2.22.7.json +0 -29
- package/releases/2.23.0.json +0 -34
- package/releases/2.24.0.json +0 -33
- package/releases/2.24.1.json +0 -33
- package/releases/2.24.2.json +0 -31
- package/releases/2.24.3.json +0 -33
- package/releases/2.25.0.json +0 -31
- package/releases/2.25.1.json +0 -33
- package/releases/2.25.2.json +0 -32
- package/releases/2.25.3.json +0 -32
- package/releases/2.26.0.json +0 -41
- package/releases/2.27.0.json +0 -38
- package/releases/2.28.0.json +0 -37
- package/releases/2.28.1.json +0 -34
- package/releases/2.29.0.json +0 -37
- package/releases/2.29.1.json +0 -34
- package/releases/2.29.2.json +0 -32
- package/releases/2.3.0.json +0 -37
- package/releases/2.30.0.json +0 -34
- package/releases/2.31.0.json +0 -39
- package/releases/2.31.1.json +0 -38
- package/releases/2.31.2.json +0 -34
- package/releases/2.31.3.json +0 -32
- package/releases/2.31.4.json +0 -33
- package/releases/2.31.5.json +0 -33
- package/releases/2.31.6.json +0 -29
- package/releases/2.31.7.json +0 -29
- package/releases/2.31.8.json +0 -33
- package/releases/2.31.9.json +0 -33
- package/releases/2.32.0.json +0 -38
- package/releases/2.33.0.json +0 -33
- package/releases/2.34.0.json +0 -38
- package/releases/2.34.1.json +0 -34
- package/releases/2.34.2.json +0 -36
- package/releases/2.34.3.json +0 -35
- package/releases/2.4.0.json +0 -37
- package/releases/2.4.1.json +0 -35
- package/releases/2.5.0.json +0 -37
- package/releases/2.6.0.json +0 -37
- package/releases/2.7.0.json +0 -37
- package/releases/2.7.1.json +0 -31
- package/releases/2.8.0.json +0 -32
- package/releases/2.8.1.json +0 -30
- package/releases/2.9.0.json +0 -33
- package/releases/2.9.1.json +0 -31
- package/releases/2.9.2.json +0 -33
- package/releases/2.9.3.json +0 -31
- package/releases/2.9.4.json +0 -37
package/releases/2.22.3.json
DELETED
|
@@ -1,32 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.22.3",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.22.3:草稿状态保持表单专属",
|
|
6
|
-
"summary": "修复 Native 编译器对 draftState 的执行校验边界,使默认与具名详情布局和公开 JSON Schema 一致地拒绝草稿工作区状态。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"默认详情布局和具名视图详情布局不再接受 draftState;该声明继续只允许出现在默认表单和具名表单上。",
|
|
10
|
-
"公开 Surface 键清单新增表单与详情的独立白名单,服务端消费者不再需要把同一 layout 白名单错误地复用于两个不同 Surface。"
|
|
11
|
-
],
|
|
12
|
-
"affectedUsers": [
|
|
13
|
-
"使用 OpenXiangda 2.0 认证草稿工作区状态的应用开发者,以及复用 Native Surface 纯校验器或键清单的平台维护人员。"
|
|
14
|
-
],
|
|
15
|
-
"upgradeSteps": [
|
|
16
|
-
"将应用对 openxiangda 的精确依赖升级到 2.22.3,按锁文件重新安装依赖,并执行 pnpm openxiangda skill install --force 刷新本地 Skill。",
|
|
17
|
-
"平台维护者应同步升级 openxiangda-contracts,并使用独立的 form/detail 键清单校验 Surface;已把 draftState 错误声明在 detail 下的配置需移回 form。"
|
|
18
|
-
],
|
|
19
|
-
"knownLimitations": [
|
|
20
|
-
"本补丁只收紧编译期与服务端 Surface 校验边界,不会自行升级平台服务、执行数据库迁移或修改已部署应用。",
|
|
21
|
-
"draftState 仍只保存受声明约束的临时工作区状态,不是业务 Data API 字段、工作流事实或永久文档存储。"
|
|
22
|
-
],
|
|
23
|
-
"issues": [],
|
|
24
|
-
"compatibility": {
|
|
25
|
-
"node": ">=24",
|
|
26
|
-
"workspaceGenerations": "v2",
|
|
27
|
-
"platform": "完整草稿工作区能力仍要求升级到支持认证草稿原子消费和 draftState Schema 的平台服务,并应用对应的 expand-only SQL migration。",
|
|
28
|
-
"v1": "V1 工作区与维护引擎不受影响。"
|
|
29
|
-
},
|
|
30
|
-
"sha256": "f0b7c256057a3366b4e4e85823f0447382f51c75e15ce11a7e4a04f15a3c8069",
|
|
31
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.22.3"
|
|
32
|
-
}
|
package/releases/2.22.4.json
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.22.4",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.22.4:connected dev 代理转发声明式应用操作路径",
|
|
6
|
-
"summary": "连接式开发代理新增按应用声明的 backend.operations 静态路径精确转发裸请求,浏览器端 applicationApiPath() 在无运行挂载元数据时也能直连本地后端,消除本地联调 404。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"openxiangda dev 代理将与应用 backend.operations[] 声明完全一致的裸路径请求转发到本地 Nest 后端(配置驱动、精确匹配,无前缀通配、不注入 authz 挂载元数据)。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [
|
|
11
|
-
"修复本地联调应用操作端点(如 /ai/console/*、/ai/risk-review-session*)404 的问题:此前代理只服务 /service 与 /api,裸 applicationApiPath 请求无法到达本地后端(协同清单 PL-09)。"
|
|
12
|
-
],
|
|
13
|
-
"affectedUsers": [
|
|
14
|
-
"使用 openxiangda dev 连接式开发且应用声明了 backend operations 的应用开发者。"
|
|
15
|
-
],
|
|
16
|
-
"upgradeSteps": [
|
|
17
|
-
"将应用对 openxiangda 的精确依赖升级到 2.22.4 并按锁文件重新安装依赖。",
|
|
18
|
-
"重跑 openxiangda dev 后,浏览器发起的裸应用操作路径(如 /ai/console/sessions)将由本地代理直达本地后端,无需改应用代码或注入挂载元数据。"
|
|
19
|
-
],
|
|
20
|
-
"knownLimitations": [
|
|
21
|
-
"仅转发与应用声明完全一致(去尾斜杠归一)的静态操作路径;未声明的裸路径仍返回 404。",
|
|
22
|
-
"未声明本地后端的前端-only 应用,命中操作路径时返回 OPENXIANGDA_CONNECTED_BACKEND_DISABLED,与既有行为一致。"
|
|
23
|
-
],
|
|
24
|
-
"issues": [],
|
|
25
|
-
"compatibility": {
|
|
26
|
-
"node": ">=24",
|
|
27
|
-
"workspaceGenerations": "v2",
|
|
28
|
-
"platform": "无平台服务依赖;代理行为变更仅影响本地开发链路。",
|
|
29
|
-
"v1": "V1 工作区不受影响。"
|
|
30
|
-
},
|
|
31
|
-
"sha256": "082690f330ed05eb91ca9dc7393eef8867c4d3c8958c701288a8bda4aaf4beef",
|
|
32
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.22.4"
|
|
33
|
-
}
|
package/releases/2.22.5.json
DELETED
|
@@ -1,31 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.22.5",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.22.5:应用侧网关断言校验跟随平台可配 TTL",
|
|
6
|
-
"summary": "应用后端 SDK 的网关断言验签器把硬编码的 30 秒寿命上限放宽到平台可配置上限(300 秒),平台网关提升断言 TTL 不再导致应用侧全量 401;防伪造上界保持。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"修复平台网关调整断言 TTL(OPENXIANGDA_GATEWAY_ASSERTION_TTL_SECONDS,30..300s)后应用侧一律返回 OPENXIANGDA_GATEWAY_ASSERTION_CONTEXT_INVALID 的问题:此前 openxiangda-nest 的 gateway-transport 验签器硬编码 exp-iat≤30s,与平台配置解耦后双端不一致(协同清单 PL-16)。"
|
|
10
|
-
],
|
|
11
|
-
"affectedUsers": [
|
|
12
|
-
"使用 openxiangda-nest 标准启动器且平台网关配置了非默认断言 TTL 的应用后端。"
|
|
13
|
-
],
|
|
14
|
-
"upgradeSteps": [
|
|
15
|
-
"应用升级 openxiangda-nest 到 2.4.11(或经 openxiangda 统一包 2.22.5 组合)并重新部署后端。",
|
|
16
|
-
"平台网关可在应用升级完成后安全地把断言 TTL 配置为 30..300 秒内的任意值;默认 30 秒不变。"
|
|
17
|
-
],
|
|
18
|
-
"knownLimitations": [
|
|
19
|
-
"自签寿命超过 300 秒的断言仍被应用侧拒绝;该上限为平台配置硬界。",
|
|
20
|
-
"断言真实有效期仍由签名、exp/nbf 与一次性 jti 保证,放宽仅针对签发窗口长度。"
|
|
21
|
-
],
|
|
22
|
-
"issues": [],
|
|
23
|
-
"compatibility": {
|
|
24
|
-
"node": ">=24",
|
|
25
|
-
"workspaceGenerations": "v2",
|
|
26
|
-
"platform": "需平台网关断言签名密钥跨重启稳定(固定 SEED);TTL 放宽只在平台同时提升 TTL 时生效。",
|
|
27
|
-
"v1": "V1 工作区不受影响。"
|
|
28
|
-
},
|
|
29
|
-
"sha256": "df1f5f4ba9e8c45bfdea6e93306d8fc89c7b3c831031989181c93d69c0c8d6b1",
|
|
30
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.22.5"
|
|
31
|
-
}
|
package/releases/2.22.6.json
DELETED
|
@@ -1,29 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.22.6",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.22.6:cli 分发模板与 2.22.5 工具链对齐",
|
|
6
|
-
"summary": "openxiangda-cli 分发模板的锁文件随 openxiangda 2.22.5 / openxiangda-nest 2.4.11 重新生成,使新建应用直接落到断言 TTL 双端一致的 SDK 组合。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"修复 cli 2.5.8 制品与本地模板内容不一致导致 release-immutability 门禁拒绝的问题:模板锁文件现随同发布单元递增(openxiangda-cli 2.5.9)。"
|
|
10
|
-
],
|
|
11
|
-
"affectedUsers": [
|
|
12
|
-
"通过 openxiangda create / cli 模板新建 2.x 应用的开发者。"
|
|
13
|
-
],
|
|
14
|
-
"upgradeSteps": [
|
|
15
|
-
"无需手动操作;新模板自动携带 openxiangda-nest 2.4.11(应用侧断言 TTL 上限跟随平台配置)。"
|
|
16
|
-
],
|
|
17
|
-
"knownLimitations": [
|
|
18
|
-
"模板锁文件对齐为随版次发布的机械变更;存量应用仍按各自锁文件升级,不受本版影响。"
|
|
19
|
-
],
|
|
20
|
-
"issues": [],
|
|
21
|
-
"compatibility": {
|
|
22
|
-
"node": ">=24",
|
|
23
|
-
"workspaceGenerations": "v2",
|
|
24
|
-
"platform": "无平台服务依赖。",
|
|
25
|
-
"v1": "V1 工作区不受影响。"
|
|
26
|
-
},
|
|
27
|
-
"sha256": "7124b2bf86fd5d3c1043fe6c27d73227403e117f72b3fe18336792d22ce36f9c",
|
|
28
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.22.6"
|
|
29
|
-
}
|
package/releases/2.22.7.json
DELETED
|
@@ -1,29 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.22.7",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.22.7:中文单字目录检索",
|
|
6
|
-
"summary": "PC 与移动目录选择器支持中文姓氏检索,避免单字输入被组件阻止发出查询。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"成员和部门选择器统一支持单个汉字,并保留普通关键词 2–64 字符约束及无效输入提示。"
|
|
10
|
-
],
|
|
11
|
-
"affectedUsers": [
|
|
12
|
-
"使用平台成员、部门选择器的 2.x 应用。"
|
|
13
|
-
],
|
|
14
|
-
"upgradeSteps": [
|
|
15
|
-
"升级 openxiangda 至 2.22.7 并重建发布应用;服务端须包含 PL-20 单汉字目录检索修复(server 2bfd3e1)。"
|
|
16
|
-
],
|
|
17
|
-
"knownLimitations": [
|
|
18
|
-
"不能仅升级应用而保留拒绝单字查询的旧平台后端;非汉字单字符仍不支持。"
|
|
19
|
-
],
|
|
20
|
-
"issues": [],
|
|
21
|
-
"compatibility": {
|
|
22
|
-
"node": ">=24",
|
|
23
|
-
"workspaceGenerations": "v2",
|
|
24
|
-
"platform": "server 2bfd3e1 或包含该提交的版本",
|
|
25
|
-
"v1": "独立 V1 不受影响。"
|
|
26
|
-
},
|
|
27
|
-
"sha256": "820e3b753c71e313a1b18697a32a0c039ff2b375c696b66ecee1c399d1a64fdf",
|
|
28
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.22.7"
|
|
29
|
-
}
|
package/releases/2.23.0.json
DELETED
|
@@ -1,34 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.23.0",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.23.0:受控文件外部处理",
|
|
6
|
-
"summary": "Nest 支持短期外部下载及未知大小的有界输出文件会话,自定义用户框架获得公开退出登录入口。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"三种 Nest DataApi 身份提供 createFileDownloadSession、initiateFileOutput、completeFileOutput。",
|
|
9
|
-
"输出使用 POST policy 约束大小、类型和暂存对象,完成后返回真实大小的受控文件引用。",
|
|
10
|
-
"openxiangda/react 公开 logoutCurrentUser 及退出回执类型,复用平台身份清理和广播。"
|
|
11
|
-
],
|
|
12
|
-
"fixes": [],
|
|
13
|
-
"affectedUsers": [
|
|
14
|
-
"需要水印、归档等服务端文件处理或自定义用户框架的 V2 应用。"
|
|
15
|
-
],
|
|
16
|
-
"upgradeSteps": [
|
|
17
|
-
"先部署包含 server 048009e 的平台版本及输出会话迁移,再升级 openxiangda 至 2.23.0 并重建应用。",
|
|
18
|
-
"外部服务按 uploadMethod=POST 和 formFields 上传 multipart,file 放最后;已完成计划直接使用 file。"
|
|
19
|
-
],
|
|
20
|
-
"knownLimitations": [
|
|
21
|
-
"输出会话目前支持 OSS 和 MinIO;COS 明确返回能力不可用。旧固定大小 PUT 上传不变。",
|
|
22
|
-
"下载签名最多300秒,授权变动不能即时撤回已签发 URL;不得记录 URL 或转发用户 Cookie。",
|
|
23
|
-
"外部服务部署、网络路由和真实业务验收独立于 npm 发布。"
|
|
24
|
-
],
|
|
25
|
-
"issues": [],
|
|
26
|
-
"compatibility": {
|
|
27
|
-
"node": ">=24",
|
|
28
|
-
"workspaceGenerations": "v2",
|
|
29
|
-
"platform": "server 048009e 或包含该提交及数据库迁移的版本",
|
|
30
|
-
"v1": "独立 V1 不受影响。"
|
|
31
|
-
},
|
|
32
|
-
"sha256": "5294829c402c9af8d0dbda1fd13b0ed33d9e38821f0f18191c92f45f1d59875d",
|
|
33
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.23.0"
|
|
34
|
-
}
|
package/releases/2.24.0.json
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.24.0",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.24.0:具名工作流草稿与稳定用户框架",
|
|
6
|
-
"summary": "为具名工作流创建操作提供私有草稿客户端;标准工作中心首次加载页面时保留用户框架。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"openxiangda/react 提供 createWorkflowFormDraftClient,按 resourceCode、workflowCode、operationCode 列出、保存和删除具名操作草稿。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [
|
|
11
|
-
"标准工作中心与标准用户页懒加载期间,加载提示留在页面内容区域,用户框架不再被整体替换。"
|
|
12
|
-
],
|
|
13
|
-
"affectedUsers": [
|
|
14
|
-
"使用具名工作流发起并需暂存表单的 V2 应用,以及使用标准用户框架的 V2 应用。"
|
|
15
|
-
],
|
|
16
|
-
"upgradeSteps": [
|
|
17
|
-
"先部署包含 server 0a8b09e 及 AddWorkflowOwnedFormDrafts 迁移的版本,再升级 openxiangda 至 2.24.0 并重建应用。",
|
|
18
|
-
"草稿客户端传入与已声明工作流创建操作一致的 workflowCode 和 operationCode;最终提交仍走具名操作。"
|
|
19
|
-
],
|
|
20
|
-
"knownLimitations": [
|
|
21
|
-
"具名草稿仅绑定该操作允许的直接字段;不支持子表草稿,不能通过原生 submit 提交。",
|
|
22
|
-
"npm 发布不代表客户平台已部署;真实经办人保存、恢复和提交仍需上线后验收。"
|
|
23
|
-
],
|
|
24
|
-
"issues": [],
|
|
25
|
-
"compatibility": {
|
|
26
|
-
"node": ">=24",
|
|
27
|
-
"workspaceGenerations": "v2",
|
|
28
|
-
"platform": "server 0a8b09e 或包含该提交及数据库迁移的版本",
|
|
29
|
-
"v1": "独立 V1 不受影响。"
|
|
30
|
-
},
|
|
31
|
-
"sha256": "9d5c5752838680a1e9ef50a06a52c1eb38aac1286cfefa9f5cc4428611b1ac2c",
|
|
32
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.24.0"
|
|
33
|
-
}
|
package/releases/2.24.1.json
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.24.1",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.24.1:具名工作流草稿与稳定用户框架",
|
|
6
|
-
"summary": "为具名工作流创建操作提供私有草稿客户端;标准工作中心首次加载页面时保留用户框架。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"openxiangda/react 提供 createWorkflowFormDraftClient,按 resourceCode、workflowCode、operationCode 列出、保存和删除具名操作草稿。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [
|
|
11
|
-
"标准工作中心与标准用户页懒加载期间,加载提示留在页面内容区域,用户框架不再被整体替换。"
|
|
12
|
-
],
|
|
13
|
-
"affectedUsers": [
|
|
14
|
-
"使用具名工作流发起并需暂存表单的 V2 应用,以及使用标准用户框架的 V2 应用。"
|
|
15
|
-
],
|
|
16
|
-
"upgradeSteps": [
|
|
17
|
-
"先部署包含 server 0a8b09e 及 AddWorkflowOwnedFormDrafts 迁移的版本,再升级 openxiangda 至 2.24.1 并重建应用。",
|
|
18
|
-
"草稿客户端传入与已声明工作流创建操作一致的 workflowCode 和 operationCode;最终提交仍走具名操作。"
|
|
19
|
-
],
|
|
20
|
-
"knownLimitations": [
|
|
21
|
-
"具名草稿仅绑定该操作允许的直接字段;不支持子表草稿,不能通过原生 submit 提交。",
|
|
22
|
-
"npm 发布不代表客户平台已部署;真实经办人保存、恢复和提交仍需上线后验收。"
|
|
23
|
-
],
|
|
24
|
-
"issues": [],
|
|
25
|
-
"compatibility": {
|
|
26
|
-
"node": ">=24",
|
|
27
|
-
"workspaceGenerations": "v2",
|
|
28
|
-
"platform": "server 0a8b09e 或包含该提交及数据库迁移的版本",
|
|
29
|
-
"v1": "独立 V1 不受影响。"
|
|
30
|
-
},
|
|
31
|
-
"sha256": "8a1bbe8c18bafee07a94704cda1770a54a2dcd12d3aa3b81703b790ccb4ed048",
|
|
32
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.24.1"
|
|
33
|
-
}
|
package/releases/2.24.2.json
DELETED
|
@@ -1,31 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.24.2",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.24.2:工作流详情进入用户界面",
|
|
6
|
-
"summary": "工作流桌面详情路由可以直接指向应用用户界面,待办和通知深链无需先进入默认后台。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"工作流 detailRouteCode.desktop 接受已声明的 admin 或 user surface;移动详情继续要求 user surface。"
|
|
10
|
-
],
|
|
11
|
-
"affectedUsers": [
|
|
12
|
-
"需要从待办或通知直接进入自定义用户审批详情的 V2 应用。"
|
|
13
|
-
],
|
|
14
|
-
"upgradeSteps": [
|
|
15
|
-
"先部署包含 server bb3ac0e 且安装新 contracts 版本的平台,再升级 openxiangda 并重新生成应用契约。",
|
|
16
|
-
"将工作流 detailRouteCode.desktop 指向路径仅含 :instanceId 的已声明 user route,重新检查和发布应用;旧 admin route 可继续使用。"
|
|
17
|
-
],
|
|
18
|
-
"knownLimitations": [
|
|
19
|
-
"深链仍要求应用登录,详情数据授权由应用服务和路由访问表达式执行;通知历史静态 URL 不会自动改写。",
|
|
20
|
-
"npm 发布与客户平台部署分别验收;真实身份点击通知和待办后还须回读目标实例。"
|
|
21
|
-
],
|
|
22
|
-
"issues": [],
|
|
23
|
-
"compatibility": {
|
|
24
|
-
"node": ">=24",
|
|
25
|
-
"workspaceGenerations": "v2",
|
|
26
|
-
"platform": "server bb3ac0e 或包含该提交和匹配 contracts 包的版本",
|
|
27
|
-
"v1": "独立 V1 不受影响。"
|
|
28
|
-
},
|
|
29
|
-
"sha256": "508815619cc6eabdd008b4016c6e7e4ff41d6c061e816bac30efbb8e66f37dad",
|
|
30
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.24.2"
|
|
31
|
-
}
|
package/releases/2.24.3.json
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.24.3",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.24.3:资源条件文本不变量",
|
|
6
|
-
"summary": "Native 资源可声明单选字段取指定值时,另一个文本字段必须包含非空白正文;平台在写入最终候选记录时统一校验。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"资源 invariants 新增有界 nonBlankTextWhenOption 表达式,只接受已声明的单选值和长短文本字段。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [],
|
|
11
|
-
"affectedUsers": [
|
|
12
|
-
"需要阻止标准管理页面或直接 Native CRUD 绕过表单校验的 V2 应用。"
|
|
13
|
-
],
|
|
14
|
-
"upgradeSteps": [
|
|
15
|
-
"先升级安装匹配 contracts 包且已部署条件不变量校验的 Native 平台服务。",
|
|
16
|
-
"逐环境盘点并按业务审批修复既有违反条件的记录,再在应用资源模型声明新规则、重新检查和发布应用。"
|
|
17
|
-
],
|
|
18
|
-
"knownLimitations": [
|
|
19
|
-
"规则只约束声明后的 Native 写入;历史记录不会被自动更改,应用读取与业务渲染仍须保持失败关闭。",
|
|
20
|
-
"规则不读取附件正文,不能用文件存在代替可审阅电子正文;npm 发布和客户平台发布分别验收。"
|
|
21
|
-
],
|
|
22
|
-
"issues": [
|
|
23
|
-
"PL-30"
|
|
24
|
-
],
|
|
25
|
-
"compatibility": {
|
|
26
|
-
"node": ">=24",
|
|
27
|
-
"workspaceGenerations": "v2",
|
|
28
|
-
"platform": "需部署支持 nonBlankTextWhenOption 的 Native Data API 和匹配 contracts 包",
|
|
29
|
-
"v1": "独立 V1 不受影响。"
|
|
30
|
-
},
|
|
31
|
-
"sha256": "34393d580f3dbc35f0ec0079192df9605074dbd2311c7271f085da7c1413d5e2",
|
|
32
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.24.3"
|
|
33
|
-
}
|
package/releases/2.25.0.json
DELETED
|
@@ -1,31 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.25.0",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.25.0:可选精确十进制字段",
|
|
6
|
-
"summary": "Native number.decimal 字段可显式启用字符串传输,保留 NUMERIC 金额精度;未启用字段沿用原有行为。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"字段声明 exactDecimal: true 时,数据契约、生成的 TypeScript 类型、标准表单、导入与工作流上下文均使用十进制字符串。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [],
|
|
11
|
-
"affectedUsers": [
|
|
12
|
-
"需要保留完整十进制精度的 V2 Native 应用;未启用该声明的应用行为不变。"
|
|
13
|
-
],
|
|
14
|
-
"upgradeSteps": [
|
|
15
|
-
"先部署包含服务端 2ed9ebd 与匹配 openxiangda-contracts 版本的平台,再在应用资源字段显式启用 exactDecimal 并重新生成、检查和发布应用。",
|
|
16
|
-
"启用字段的应用读写必须发送规范十进制字符串,不能把金额转换为 JavaScript number。"
|
|
17
|
-
],
|
|
18
|
-
"knownLimitations": [
|
|
19
|
-
"本版只提供精确字段传输,不提供主子合同额度预留、释放或父占额授权原语;相关业务入口应继续关闭。",
|
|
20
|
-
"npm 包发布与客户平台部署分别验收;真实业务数据读写需在应用的受权测试环境独立验证。"
|
|
21
|
-
],
|
|
22
|
-
"issues": [],
|
|
23
|
-
"compatibility": {
|
|
24
|
-
"node": ">=24",
|
|
25
|
-
"workspaceGenerations": "v2",
|
|
26
|
-
"platform": "服务端 2ed9ebd 或后续包含该提交且安装匹配 contracts 包的版本",
|
|
27
|
-
"v1": "独立 V1 不受影响。"
|
|
28
|
-
},
|
|
29
|
-
"sha256": "a007d4e4b503fbfe6ce6100e5b41b201409d3b63b9319310db3ef0c57606839a",
|
|
30
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.25.0"
|
|
31
|
-
}
|
package/releases/2.25.1.json
DELETED
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.25.1",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.25.1:精确十进制契约对齐",
|
|
6
|
-
"summary": "补齐可选精确十进制字段的公开 Schema 与共享 contracts 包版本,并声明 Native 十进制额度预留动作的受限契约。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"Native 精确十进制额度预留动作提供有界声明和请求契约;编译器校验资源字段、状态及同资源动作的金额映射冲突。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [
|
|
11
|
-
"公开字段 Schema 中的 exactDecimal 与共享 contracts 包的字段清单、生成 Action 和资源 Schema 保持一致。"
|
|
12
|
-
],
|
|
13
|
-
"affectedUsers": [
|
|
14
|
-
"显式启用 exactDecimal 的 V2 Native 应用和准备使用额度预留动作的开发者;未启用这些能力的应用行为不变。"
|
|
15
|
-
],
|
|
16
|
-
"upgradeSteps": [
|
|
17
|
-
"先发布并部署匹配的 contracts 包与平台服务端,再生成和发布使用 exactDecimal 的应用。",
|
|
18
|
-
"额度预留动作只有在目标平台完成对应运行时部署及真实业务验收后才能启用。"
|
|
19
|
-
],
|
|
20
|
-
"knownLimitations": [
|
|
21
|
-
"本版工具链提供声明和请求契约,不单独证明额度预留动作在任何客户生产环境已经可用。",
|
|
22
|
-
"npm 包发布、平台部署和应用真实角色验收分别记录。"
|
|
23
|
-
],
|
|
24
|
-
"issues": [],
|
|
25
|
-
"compatibility": {
|
|
26
|
-
"node": ">=24",
|
|
27
|
-
"workspaceGenerations": "v2",
|
|
28
|
-
"platform": "需要部署支持精确十进制字段及相应动作契约的匹配平台服务端",
|
|
29
|
-
"v1": "独立 V1 不受影响。"
|
|
30
|
-
},
|
|
31
|
-
"sha256": "23677498fc26073ccfedbbfe25871b3f1cd24525b72dcd0f580207c8e75be602",
|
|
32
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.25.1"
|
|
33
|
-
}
|
package/releases/2.25.2.json
DELETED
|
@@ -1,32 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.25.2",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.25.2:标准工作中心视图深链",
|
|
6
|
-
"summary": "标准工作中心可从 PC 或移动端链接直接打开我创建的、待我审批、我已处理或抄送我的视图。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"标准工作中心支持 view=created、pending、handled、cc 查询参数,切换标签时同步 URL。"
|
|
9
|
-
],
|
|
10
|
-
"fixes": [
|
|
11
|
-
"不支持的 view 参数回退到待我审批,不会传入 Workflow 列表请求。"
|
|
12
|
-
],
|
|
13
|
-
"affectedUsers": [
|
|
14
|
-
"使用 OpenXiangda 2.0 标准工作中心的 PC 和移动端应用;无参数入口仍默认为待我审批。"
|
|
15
|
-
],
|
|
16
|
-
"upgradeSteps": [
|
|
17
|
-
"应用更新到 openxiangda@2.25.2 并重新构建发布后,可将我的申请入口链接设为 /work-center?view=created 或移动端 /m/work-center?view=created。",
|
|
18
|
-
"以目标环境的具名用户读取列表,确认视图数据仍由 Workflow API 的当前用户授权决定。"
|
|
19
|
-
],
|
|
20
|
-
"knownLimitations": [
|
|
21
|
-
"此版不改变平台服务端授权、工作流数据或任何旧应用的现有链接;应用预发部署与具名角色验收需分别记录。"
|
|
22
|
-
],
|
|
23
|
-
"issues": [],
|
|
24
|
-
"compatibility": {
|
|
25
|
-
"node": ">=24",
|
|
26
|
-
"workspaceGenerations": "v2",
|
|
27
|
-
"platform": "兼容已有 Workflow Work Center v2 API,无需服务端升级",
|
|
28
|
-
"v1": "独立 V1 不受影响。"
|
|
29
|
-
},
|
|
30
|
-
"sha256": "b7b77167c479d809e72fc0c1cd980a36f491fa4639cf259510b0ad1b0a94f1b7",
|
|
31
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.25.2"
|
|
32
|
-
}
|
package/releases/2.25.3.json
DELETED
|
@@ -1,32 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.25.3",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.25.3:浏览器跨标签身份重核",
|
|
6
|
-
"summary": "应用标签重新获得焦点时,先读取平台当前身份与权限,避免旧页面继续展示原账号的功能。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"返回应用标签时重核当前授权;主体或权限作用域变化时停用旧页面,显示明确提示并要求用户确认后进入新身份。",
|
|
10
|
-
"同身份重核保留未保存表单,重核失败或退出广播发生时不继续使用旧授权。"
|
|
11
|
-
],
|
|
12
|
-
"affectedUsers": [
|
|
13
|
-
"使用 OpenXiangda 2.0 浏览器运行时的应用,尤其是同一浏览器中切换登录账号或权限发生变化的用户。"
|
|
14
|
-
],
|
|
15
|
-
"upgradeSteps": [
|
|
16
|
-
"应用更新到 openxiangda@2.25.3 后重新构建发布;CLI 对应版本为 openxiangda-cli@2.5.19。",
|
|
17
|
-
"在预发环境以具名管理员和经办人双向切换标签,核对旧页面停用、未保存表单保护及当前角色能力。"
|
|
18
|
-
],
|
|
19
|
-
"knownLimitations": [
|
|
20
|
-
"重核在标签重新获得焦点或变为可见时触发;停留在前台的其他标签登录变更不会主动推送到当前页面。",
|
|
21
|
-
"应用预发部署与具名角色验收需单独记录。"
|
|
22
|
-
],
|
|
23
|
-
"issues": [],
|
|
24
|
-
"compatibility": {
|
|
25
|
-
"node": ">=24",
|
|
26
|
-
"workspaceGenerations": "v2",
|
|
27
|
-
"platform": "使用现有 authz/current API,无需服务端升级",
|
|
28
|
-
"v1": "独立 V1 不受影响。"
|
|
29
|
-
},
|
|
30
|
-
"sha256": "9dde692d0419326b98aa15648a78af7538668fd18cd516b0fcd3fdf3f4908249",
|
|
31
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.25.3"
|
|
32
|
-
}
|
package/releases/2.26.0.json
DELETED
|
@@ -1,41 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.26.0",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.26.0:原操作恢复、目标预检与类型化资源",
|
|
6
|
-
"summary": "保留未知提交的原操作,提前汇总目标环境缺项,提供类型化资源、受限角色候选和可复制的安全请求诊断。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"标准 PC/移动审批提交在响应未知时保留原操作定位信息,刷新后读取原回执;同一页面可按原键和冻结输入显式恢复,避免生成新键重复提交。",
|
|
9
|
-
"生成 ResourceTypes 并为 Nest 当前用户、业务动作和事件上下文提供资源绑定,约束资源名、字段、引用和更新 revision。",
|
|
10
|
-
"受信业务动作可读取声明角色的最小候选信息,服务端限定租户、环境、角色和有效期,提交时仍重新授权。"
|
|
11
|
-
],
|
|
12
|
-
"fixes": [
|
|
13
|
-
"check/deploy 在构建前集中输出目标能力与配置缺项,附实际目标、版本、观测时间和 requestId;诊断信息不会混入封闭的平台响应契约。",
|
|
14
|
-
"新建应用和可选后端依赖安装失败保留安全错误分类与恢复提示,安装有界且不回显 registry 凭据。",
|
|
15
|
-
"浏览器请求、导出与授权刷新统一保留安全请求定位信息;网络写入结果未知时不自动重放。"
|
|
16
|
-
],
|
|
17
|
-
"affectedUsers": [
|
|
18
|
-
"使用 OpenXiangda 2.0 开发、交付或运行标准业务审批的应用。",
|
|
19
|
-
"需要类型化 Native 资源绑定及业务角色候选的受管 Nest 扩展。"
|
|
20
|
-
],
|
|
21
|
-
"upgradeSteps": [
|
|
22
|
-
"应用固定 openxiangda@2.26.0,更新锁文件,重新生成契约并运行适用的 check/test。CLI 配套版本为 openxiangda-cli@2.5.20。",
|
|
23
|
-
"先读取目标环境能力。启用原流程回执恢复需要 business-process.original-resolution@1.0.0;角色候选需要 directory.assignment-candidates@1.0.0。缺少能力时先升级目标服务端,不猜测接口。",
|
|
24
|
-
"预发验证提交响应丢失、刷新后原键查询、已撤销权限拒绝,以及业务实际用到的资源与角色。复用同一已验收候选晋级。"
|
|
25
|
-
],
|
|
26
|
-
"knownLimitations": [
|
|
27
|
-
"未观察到原命令不证明事务回滚;恢复界面保留原键。刷新后不持久保存业务表单内容,也不自动重放未知写入。",
|
|
28
|
-
"请求定位信息本身不授予读取后台日志或其他用户操作的权限。",
|
|
29
|
-
"类型、诊断和本地工具改进不要求无关平台升级;新增服务端协议需目标明确公布对应能力。",
|
|
30
|
-
"npm 发行验证不代替客户部署、真实角色或外部通知、签署和文件的业务验收。"
|
|
31
|
-
],
|
|
32
|
-
"issues": [],
|
|
33
|
-
"compatibility": {
|
|
34
|
-
"node": ">=24",
|
|
35
|
-
"workspaceGenerations": "v2",
|
|
36
|
-
"platform": "保留现有平台基础协议;原流程恢复与受限角色候选按能力协商,分别需要 business-process.original-resolution@1.0.0 和 directory.assignment-candidates@1.0.0。",
|
|
37
|
-
"v1": "独立 V1 引擎与工作区不受影响。"
|
|
38
|
-
},
|
|
39
|
-
"sha256": "a26725320f8477e8829fc0b22e50b67e4f54da7978c9b5972924f954fbb7891f",
|
|
40
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.26.0"
|
|
41
|
-
}
|
package/releases/2.27.0.json
DELETED
|
@@ -1,38 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.27.0",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.27.0:精确额度审批生命周期",
|
|
6
|
-
"summary": "补齐主子记录精确金额占用的审批终态声明、原轮次事务参数及撤回修订重提接入,保持平台对金额、身份和审批事实的统一校验。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"HTTP 事件订阅可声明同资源审批的额度终态:通过继续占额,驳回或撤回释放;两侧编译器共同校验审批、资源、状态和固定迁移模式。",
|
|
9
|
-
"Native 事务支持绑定原 reservationKey、transitionKey 和唯一子记录 update,Nest 继承已验证的事件上下文,不允许客户端自报额度迁移模式。",
|
|
10
|
-
"提供本人 FormDraft 与 BusinessProcess update 重提组合示例,将修改正式金额、重新占额、消费草稿和生成审批命令放在同一平台事务。"
|
|
11
|
-
],
|
|
12
|
-
"fixes": [
|
|
13
|
-
"事件终态声明参与能力使用摘要;目标必须满足 data.decimal-reservations@1.1.0,不能把仅有数据表和通用防护的旧服务端当作完整额度能力。"
|
|
14
|
-
],
|
|
15
|
-
"affectedUsers": [
|
|
16
|
-
"需要以主记录金额约束多条子记录,并在审批通过、驳回、撤回和重提间管理额度的 OpenXiangda 2.0 应用。"
|
|
17
|
-
],
|
|
18
|
-
"upgradeSteps": [
|
|
19
|
-
"应用固定 openxiangda@2.27.0,更新锁文件,重新生成契约并执行适用检查;平台同步升级匹配的公共编译器、额度实现和向前迁移。",
|
|
20
|
-
"在实际资源和审批中声明 reserve 动作及终态订阅,先确认没有未入账的历史子记录。保留未完成请求的原幂等键和输入。",
|
|
21
|
-
"预发验证并发超额、精确小数、权限拒绝、通过保留占额、释放一次及同记录修订重提。真实验收前保持额度入口禁用。"
|
|
22
|
-
],
|
|
23
|
-
"knownLimitations": [
|
|
24
|
-
"普通 CRUD 不开放 released 子记录保护字段写入;修订先保存本人草稿,再通过原子 update 重提。",
|
|
25
|
-
"作废或终止需要另行实现真实受管业务动作,签后金额变更不在首批能力内。旧轮次事件不能释放新轮次额度。",
|
|
26
|
-
"原回执重放仍要求当前授权、有效事件租约和父记录可读性。",
|
|
27
|
-
"公开包发行不是客户部署或业务验收,不提供应用侧浮点求和替代台账的降级路径。"
|
|
28
|
-
],
|
|
29
|
-
"issues": [],
|
|
30
|
-
"compatibility": {
|
|
31
|
-
"node": ">=24",
|
|
32
|
-
"workspaceGenerations": "v2",
|
|
33
|
-
"platform": "额度应用要求 data.decimal-reservations@1.1.0,并使用与目标平台一致的共享编译器。未启用额度的应用保持原有行为。",
|
|
34
|
-
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
35
|
-
},
|
|
36
|
-
"sha256": "ff07310ebff47f32988ba6c6117f0072daca6497700c8f24ed1c10c92c081b06",
|
|
37
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.27.0"
|
|
38
|
-
}
|
package/releases/2.28.0.json
DELETED
|
@@ -1,37 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.28.0",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.28.0:应用原操作自助诊断",
|
|
6
|
-
"summary": "应用管理员通过现有工作区查询原请求、持久命令、部署和受管文件的脱敏事实,减少依赖平台人员登录服务器定位问题的情况。",
|
|
7
|
-
"newFeatures": [
|
|
8
|
-
"logs 增加 request-id、command-id、deployment-run-id、file-id 四种互斥定位器,MCP 提供相同范围的 application_diagnostics 只读工具。",
|
|
9
|
-
"结果显示实际站点、应用、环境、时间窗口及观测时间;SDK 校验查询与响应关联,只保留受支持的元数据。"
|
|
10
|
-
],
|
|
11
|
-
"fixes": [
|
|
12
|
-
"明确区分已观测、未观测和诊断暂不可用;未知结果不再被解释成原操作未执行,也不会触发换键重放。"
|
|
13
|
-
],
|
|
14
|
-
"affectedUsers": [
|
|
15
|
-
"需要按原操作 ID 自助排查发布、工作流和文件状态的 OpenXiangda 2.0 应用管理员及开发者。"
|
|
16
|
-
],
|
|
17
|
-
"upgradeSteps": [
|
|
18
|
-
"应用消费 openxiangda@2.28.0 并更新锁文件;使用已有工作区开发者登录,不需要服务器账号。",
|
|
19
|
-
"平台应提供 application.scoped-diagnostics@1;查询默认使用 test,生产环境需显式传 --environment production。",
|
|
20
|
-
"保留原操作 ID。request-id 默认查询最近一小时,也可传一对 UTC from/to,窗口最多 24 小时;其他定位器不接受时间窗口。"
|
|
21
|
-
],
|
|
22
|
-
"knownLimitations": [
|
|
23
|
-
"诊断受应用管理权限和当前租户、环境约束;普通应用服务凭据不因此获得管理权限。",
|
|
24
|
-
"每次最多返回 50 条事实,可能标记截断;不返回业务正文、文件名、原始日志或密钥。",
|
|
25
|
-
"未观测不表示原写入未发生,已观测不表示业务验收完成。暂不可用时保留原键与输入,按提示继续查询。",
|
|
26
|
-
"此次新增能力不改变共享 Native 编译器摘要;公开包发行与实际站点部署分别验证。"
|
|
27
|
-
],
|
|
28
|
-
"issues": [],
|
|
29
|
-
"compatibility": {
|
|
30
|
-
"node": ">=24",
|
|
31
|
-
"workspaceGenerations": "v2",
|
|
32
|
-
"platform": "新诊断入口要求 application.scoped-diagnostics@1.0.0 或兼容 1.x;原 logs [deploymentId] 和未使用此能力的应用保持原行为。",
|
|
33
|
-
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
34
|
-
},
|
|
35
|
-
"sha256": "80c18512f5cb76850e738b9e802261af68e27f6582b3f686781da7c9d4367c2a",
|
|
36
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.28.0"
|
|
37
|
-
}
|
package/releases/2.28.1.json
DELETED
|
@@ -1,34 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
-
"version": "2.28.1",
|
|
4
|
-
"status": "reviewed",
|
|
5
|
-
"title": "OpenXiangda 2.28.1:后端镜像原制品上传恢复",
|
|
6
|
-
"summary": "上传中断后保留原 OCI 镜像,普通 deploy 重试直接从平台已有偏移或 ready 回执恢复,减少重建和重复传输。",
|
|
7
|
-
"newFeatures": [],
|
|
8
|
-
"fixes": [
|
|
9
|
-
"已导出的后端镜像不会再因为上传失败或响应丢失被立即删除;相同输入重试保持原摘要,已封存候选不再依赖 Docker 重建。",
|
|
10
|
-
"缓存绑定当前站点、租户、用户、应用环境和实际构建上下文,包含未提交源码;恢复前验证全部 blob,使用跨进程租约阻止重复上传。"
|
|
11
|
-
],
|
|
12
|
-
"affectedUsers": [
|
|
13
|
-
"通过平台登录态分块上传后端镜像的 OpenXiangda 2.0 应用开发者。"
|
|
14
|
-
],
|
|
15
|
-
"upgradeSteps": [
|
|
16
|
-
"应用消费 openxiangda@2.28.1 并更新锁文件。上传中断时保留工作区输入,恢复网络或登录后重复原 deploy 命令。",
|
|
17
|
-
"无需平台数据库迁移,也无需手工寻找 BuildKit 历史或镜像上传会话。"
|
|
18
|
-
],
|
|
19
|
-
"knownLimitations": [
|
|
20
|
-
"最多保留 8 个候选、总预留空间 8 GiB、24 小时;平台单镜像上限超过 8 GiB 时继续原临时上传路径。缓存过期或被预算清理后需要重新构建。",
|
|
21
|
-
"源码、身份、环境、配置或工具版本变化会形成新候选;恢复原镜像不重新求值远程 FROM/RUN 输入。",
|
|
22
|
-
"本机上下文校验有 100000 条目、8 GiB、60 秒预算;构建期间源码变化会拒绝上传,需要保存完成后重试。",
|
|
23
|
-
"真实 Docker 导出及故障恢复、隔离的传输协议和发行门禁分别验证,不代表任何客户应用已发布或通过业务验收。"
|
|
24
|
-
],
|
|
25
|
-
"issues": [],
|
|
26
|
-
"compatibility": {
|
|
27
|
-
"node": ">=24",
|
|
28
|
-
"workspaceGenerations": "v2",
|
|
29
|
-
"platform": "复用既有 backendImageUpload 协议和 auth/whoami,不新增远端上传状态或服务器账号要求。",
|
|
30
|
-
"v1": "独立 V1 引擎和工作区不受影响。"
|
|
31
|
-
},
|
|
32
|
-
"sha256": "762fa08d9c2818264ed9b65383f1ec60ad6bc4236978ee07cf0c19cdce45ad16",
|
|
33
|
-
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.28.1"
|
|
34
|
-
}
|