openxiangda 2.59.1 → 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/components/resource/generated-resource-definition.d.ts +1 -0
- package/dist/browser/components/resource/generated-resource-definition.d.ts.map +1 -1
- package/dist/browser/components/resource/resource-form-operations.d.ts.map +1 -1
- package/dist/browser/components/resource/resource-form-operations.js +3 -2
- package/dist/browser/components/resource/resource-form-operations.js.map +1 -1
- package/dist/browser/runtime-authorization-recovery.d.ts.map +1 -1
- package/dist/browser/runtime-authorization-recovery.js +3 -1
- package/dist/browser/runtime-authorization-recovery.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/field-components.md +7 -0
- package/documentation/getting-started.md +7 -7
- package/documentation/managed-concurrency-frontend.md +1 -1
- package/documentation/manifest.json +5 -5
- package/documentation/workflow-events.md +25 -0
- package/package.json +22 -29
- 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.2.json +33 -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/field-components.md +7 -0
- package/skills/openxiangda-v2/references/getting-started.md +7 -7
- package/skills/openxiangda-v2/references/managed-concurrency-frontend.md +1 -1
- package/skills/openxiangda-v2/references/workflow-events.md +25 -0
- 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,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "字段权限引用与开发态契约加载修复",
|
|
6
|
+
"summary": "字段复用已有权限时保留真实目录所有者,消除资源顺序影响;连接开发的后端读取当前生成源码契约。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"普通业务字段的 read/create/update 可复用显式或其他资源的 CRUD capability,保持唯一目录定义。",
|
|
10
|
+
"声明、契约生成与共享 Native 编译器采用相同定义优先规则,继续拒绝真实 owner 冲突和跨应用引用。",
|
|
11
|
+
"连接开发后端采用 openxiangda-source 条件加载当前源码,保留 Node 选项,避免新 operation 被旧构建输出遗漏。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用私有字段投影、跨资源权限或连接开发后端的 V2 应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"本轮仅导出完整同源本地测试七包,不执行 npm 发布。",
|
|
18
|
+
"更新精确根包及完整配套依赖,验证目标兼容性、本人行/字段权限和连接开发后端启动。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"源码修复和包检查不替代应用真实角色、文件与业务验收。",
|
|
22
|
+
"应用仍须声明运行时授权规则;本修复不会赋予新的业务权限。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "共享 Native 编译器完整同源配套;稳定 1.x 不变"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "2af2124516e3a440a5f078ddfd95280bd52e1f2e84ad59297123c98f88c9263c",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.2"
|
|
31
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "按业务范围维护流程职责",
|
|
6
|
+
"summary": "成员管理支持有效审批与抄送流程中的范围职责,避免必须增加无关的数据策略才能维护审批人。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"范围目录返回有效流程绑定、兼容节点覆盖、补充路由和在途固定版本的职责来源。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"SDK 成员选择器识别仅用于流程的范围角色,并继续按每条数据策略处理不受限角色排除。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"按学院、部门等业务范围配置审批和抄送人员的 V2 应用开发者与管理员。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"本轮导出同源的完整本地测试七包,不执行 npm 发布。",
|
|
18
|
+
"更新精确根包与配套依赖,并使用支持 Workflow 范围适用性的 V2 Server。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"职责范围维护不授予普通数据读写、应用管理或额外菜单权限。",
|
|
22
|
+
"已创建任务的参与人快照保持原语义;本地平台回归不代表学校真实流程验收。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "同源 Native 编译器与 Workflow 范围适用性服务;稳定 1.x 不受影响"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "fa74e19fb94432a9b2c5765c216512b1fa8dabfc094e8e06ddaf88600851ada9",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.3"
|
|
31
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.4",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "统一入口校验 Native 事务",
|
|
6
|
+
"summary": "应用业务测试可以从统一根包读取共享事务校验器,验证实际生成的守卫而无需额外依赖底层实现包。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"openxiangda/testing 导出 validateDataTransactionRequest 与 SCHEMA_VERSIONS,保留共享合同诊断。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"补齐统一依赖约束下业务事务测试缺少受支持校验入口的问题。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"编写 Native 原子事务和 BusinessProcess 提交业务测试的 V2 应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"消费同源精确根包后从 openxiangda/testing 导入,不添加底层包依赖。",
|
|
18
|
+
"本轮仅导出本地密封测试分发,不执行 npm 发布。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"合同诊断不替代真实权限、数据库并发、业务运行和恢复验收。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "Native 事务合同不变,稳定 1.x 不受影响"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "2ddc0a54c3ded4aeb9b33c98ae7ed43007653097dabd9ee10e3b68ff6998b83d",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.4"
|
|
30
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.5",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "单人资料的条件唯一约束",
|
|
6
|
+
"summary": "Native 唯一键可以按平台用户的稳定身份和布尔启用条件约束有效资料,并由数据库处理并发冲突。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"user.single 支持 exact-v1 唯一键;布尔字段支持 eq/ne 条件。",
|
|
9
|
+
"仅使用新增声明时要求 data.unique-keys 1.1.0,既有规则维持原能力要求。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要每人仅一份有效资料、同时保留停用历史的 V2 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"使用精确同源 SDK 和支持 data.unique-keys 1.1.0 的平台;通过普通模型声明安装规则。",
|
|
17
|
+
"历史有效资料重复时先按业务处理冲突,平台不会自动删除或停用记录。",
|
|
18
|
+
"本轮仅导出本地密封分发,不执行 npm 发布。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"NULL 不参与布尔 eq/ne 条件;规则仍限 8 个,每个最多 4 字段和 4 条件。",
|
|
22
|
+
"已安装规则的删除仍需托管迁移,不通过普通旧版本激活移除。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "新增声明要求 data.unique-keys 1.1.0;稳定 1.x 与既有唯一键规则不变"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "033fd95bf90f5e242f030ee1b24688dc5358aace39a4477977eb25f08c158429",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.5"
|
|
31
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.6",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "基础唯一键的平台预检兼容修复",
|
|
6
|
+
"summary": "修复基础唯一键应用在已支持增强合同的平台上被能力预检误拒,保留实际使用派生及严格边界。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"data.unique-keys要求1.0.0时可使用available的1.1.0平台;不推断未知版本或其他能力的兼容性。"
|
|
10
|
+
],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"使用既有文本条件唯一键并连接支持data.unique-keys 1.1.0平台的V2开发者。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"按精确完整根发行升级并保留旧锁文件,重新运行目标检查或部署。",
|
|
16
|
+
"应用继续声明原业务唯一键,不修改共享编译器派生的能力要求或删除约束。",
|
|
17
|
+
"本轮仅导出本机完整发行,不执行npm或学校生产发布。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"要求1.1.0仍不能使用1.0.0平台;preview/planned/缺失及未知版本继续拒绝。",
|
|
21
|
+
"能力预检不替代平台准备、激活与真实业务验收。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "既有data.unique-keys 1.0.0与已实现1.1.0的已知兼容关系;validator及应用唯一键语义不变"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "662caf90440646203a04f8cf2398a146cc895fc7259a4f5514786f83a63868ab",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.6"
|
|
30
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.8",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "基础唯一键制品合同与编译器派生一致",
|
|
6
|
+
"summary": "修复制品封装对基础唯一键1.0.0的误拒,保留增强1.1.0以及精确使用闭包校验。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"contracts制品语法接受共享编译器实际派生的data.unique-keys基础1.0.0及现行1.1.0。",
|
|
10
|
+
"增加实际compileAppPackage回归,覆盖基础与增强唯一键从配置到制品的完整链路。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用基础唯一键且目标平台已实现增强1.1.0能力的2.0应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"使用精确完整根发行升级,并配套已修复的Server入站制品校验。",
|
|
17
|
+
"重新检查和部署原应用;保留编译器派生需求,不手改contractVersion、usageDigest或唯一键声明。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"未知能力、未知版本及其他能力版本差异仍拒绝;语法接受不代表目标能力或部署成功。",
|
|
21
|
+
"增强声明降级为基础仍由精确配置闭包拒绝;权限、数据库唯一约束与激活Head保持原边界。",
|
|
22
|
+
"本批仅本机完整SDK分发,不执行npm或学校生产发布。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [
|
|
25
|
+
"PLT-013"
|
|
26
|
+
],
|
|
27
|
+
"compatibility": {
|
|
28
|
+
"node": ">=24",
|
|
29
|
+
"platform": "需配套Server338d5ac3;不改变共享compiler派生、validatorDigest或1.x引擎"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "3cd0baea28368559da50567109bd7fb991089ed4ba00f03f3ffa772108cd24dd",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.8"
|
|
33
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.9",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "受管视频与音频播放器",
|
|
6
|
+
"summary": "补齐标准文件页的媒体播放,提供拥有鉴权读取与内容生命周期的Field Kit内嵌播放器。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"新增ManagedMediaPlayer,接收平台文件引用并按当前身份读取媒体,提供加载、拒绝和重试状态。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"video/audio的合法inline预览不再落入无预览器分支。",
|
|
12
|
+
"文件、资源、身份或绑定变化与卸载释放ObjectURL,迟到响应不会展示原媒体。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"在2.0应用中观看托管视频或音频、迁移原课时视频弹窗的开发者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"升级完整根发行,在原任务界面使用openxiangda/field-kit的ManagedMediaPlayer。",
|
|
19
|
+
"传入正式resourceCode与DataFileRef;保留显式学习提交,不根据播放状态改写业务进度。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"内嵌播放器默认单文件100MiB;浏览器编码支持由实际媒体决定,需真实播放验收。",
|
|
23
|
+
"不增加流式转码、范围读取或观看时长规则,权限继续由原Native文件API控制。",
|
|
24
|
+
"本轮仅本机完整SDK配套,不执行npm或学校生产发布。"
|
|
25
|
+
],
|
|
26
|
+
"issues": [
|
|
27
|
+
"PLT-014"
|
|
28
|
+
],
|
|
29
|
+
"compatibility": {
|
|
30
|
+
"node": ">=24",
|
|
31
|
+
"platform": "复用现有DataFilePreview和Native文件授权,不改变compiler、数据模型或1.x引擎"
|
|
32
|
+
},
|
|
33
|
+
"sha256": "6258c81bf6fe452133e118982cefc432bbab138629d12908602523c2e04f8ba4",
|
|
34
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.9"
|
|
35
|
+
}
|
|
@@ -0,0 +1,37 @@
|
|
|
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
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.50.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "按业务资料权限查看流程办理历史",
|
|
6
|
+
"summary": "业务查看组可以在当前资料范围内查看原固定流程的节点、办理人、时间和意见,审批授权保持独立。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型新增workflowHistory显式声明,按同一成员同时持有资料读取和全部历史能力校验。",
|
|
9
|
+
"公开loadWorkflowRecordHistory与PC/手机WorkflowRecordHistoryPanel,标准Native详情可按声明展开记录。",
|
|
10
|
+
"有界安全投影不返回事实、业务值、代码、角色席位、原detail或操作令牌;分页、容量与一致性冲突有明确失败。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"需要业务查看职责、本人记录范围和独立历史授权的V2应用。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"安装同源本地包组合;声明历史能力并在模型workflowHistory.read中引用。",
|
|
18
|
+
"平台Server需提供workflow.record-history-read@1.0.0后再部署新声明;旧固定实例沿当前Native资料权限读取。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"没有npm发布、学校业务写入或生产部署。",
|
|
22
|
+
"服务端20项定向测试、5项编译测试和独立PG11项真实查询/fixture RLS通过;完整应用六组当前角色矩阵及两端运行仍待验。",
|
|
23
|
+
"源评论、打印和删除不由本历史接口实现。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"platform": "workflow.record-history-read@1.0.0;未声明workflowHistory的应用继续原合同。"
|
|
29
|
+
},
|
|
30
|
+
"sha256": "b07d99099c55cad220f613f90c368e456bd6a698b8fa18cda3554d7ee0153c15",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.50.0"
|
|
32
|
+
}
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.52.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "独立授权的单记录资料打印",
|
|
6
|
+
"summary": "标准资料详情提供PC与手机打印预览,读取和打印均使用当前身份的独立打印许可及原数据范围。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型新增可选 recordPrint 声明,编译器同源派生 data.record-print@1.0.0。",
|
|
9
|
+
"平台先筛选同一成员的资料读取和全部打印能力,再执行原RLS、Perspective、字段权限与脱敏。",
|
|
10
|
+
"公开 loadNativeRecordPrint 与 ResourceRecordPrintPreview,标准详情直接提供打印入口;打印前重新读取当前资料,失败和身份变化清除旧预览。",
|
|
11
|
+
"CLI模板随根包更新精确SDK依赖;平台能力自动注册,不增加初始化SQL、开关或数据表。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"需要为业务资料配置独立打印权限的V2应用及维护者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"消费同源SDK、contracts及devkit,使用提供 data.record-print@1.0.0 的Server。",
|
|
19
|
+
"声明 recordPrint.read、同应用能力及对应职责,沿既有资料范围和字段规则配置打印许可。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"尚未发布npm;真实应用六组权限和PC/390px浏览器验收待共享平台空闲。",
|
|
23
|
+
"当前只支持主记录;可读子表明确返回409,PDF模板、完整子表快照、签章和源打印模板等价另行实现。",
|
|
24
|
+
"附件及图片打印名称和大小,富文本转安全文本;不自动下载附件。",
|
|
25
|
+
"独立许可保护平台打印接口与标准入口;已读取资料的截图或浏览器自行打印不由平台阻止。"
|
|
26
|
+
],
|
|
27
|
+
"issues": [],
|
|
28
|
+
"compatibility": {
|
|
29
|
+
"node": ">=24",
|
|
30
|
+
"platform": "data.record-print@1.0.0;未声明应用继续原行为,已有流程定义及历史实例不迁绑。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "d14d28435c971794fae5bc2b939600bf0cb29a77822ed54827817b45200f5b0e",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.52.0"
|
|
34
|
+
}
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.53.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "独立授权的单记录资料评论",
|
|
6
|
+
"summary": "标准详情提供单记录评论,读取和新增分别声明,同一成员的数据范围与当前用户授权控制服务端执行。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型可选recordComments分别配置read/create,编译器自动派生data.record-comments@1.0.0,fresh/update自动执行正式SQL迁移。",
|
|
9
|
+
"平台单记录有界分页、纯文本新增及本人原键回执接口,评论不修改主记录或工作流意见。",
|
|
10
|
+
"公开列表、新增、回执SDK及ResourceRecordComments标准面板,提交不确定时锁定原键并先核对结果。",
|
|
11
|
+
"记录锁与唯一约束保障并发容量及幂等,来源版本与评论回执原子保存。CLI模板随SDK精确升级。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"需要独立资料评论权限的V2应用及平台维护者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"消费同源SDK/contracts/devkit与提供data.record-comments@1.0.0的Server,走正式SQL迁移链。",
|
|
19
|
+
"声明recordComments、同应用能力与职责,保留原资料范围;应用不要为评论另建权限或绕开主记录mutationOwner。",
|
|
20
|
+
"未知结果保留原请求并查本人回执,仅回执不存在时显式同键重试。"
|
|
21
|
+
],
|
|
22
|
+
"knownLimitations": [
|
|
23
|
+
"未发布npm,实际六组应用授权、普通app-admin与PC/390px浏览器验收待共享平台空闲。",
|
|
24
|
+
"当前仅纯文本评论,不含回复、附件、提及、编辑/删除、通知及旧评论导入;源端附加语义尚未运行核实。",
|
|
25
|
+
"页内导航和关闭浏览器有未完成保护;当前不支持跨刷新自动续写,需保留原键和正文并通过SDK查询原结果。"
|
|
26
|
+
],
|
|
27
|
+
"issues": [],
|
|
28
|
+
"compatibility": {
|
|
29
|
+
"node": ">=24",
|
|
30
|
+
"platform": "data.record-comments@1.0.0;正式expand SQL新增附属表,未声明应用与已有流程实例保持原行为。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "6f06443044f74eec12049a8e7c208a84a70a958be5f4495bbdc42e4e953a9184",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.53.0"
|
|
34
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.54.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "按资料权限受控删除关联流程",
|
|
6
|
+
"summary": "标准详情提供显式的资料删除影响预览与确认,沿同一成员的资料范围复用 Native 事务和 Workflow Kernel 的删除命令与回执。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型可选 recordDeletion.delete,声明自动派生 data.workflow-record-deletion@1.0.0,无需额外初始化开关。",
|
|
9
|
+
"同一成员须同时拥有资料 read、delete 和全部维护能力,保留原行权限,不授普通编辑或通用流程管理员权。",
|
|
10
|
+
"公开预览、执行、原回执 SDK 与标准详情弹层;未知结果固定原键、原因和预览,先恢复结果。",
|
|
11
|
+
"无关联实例沿 Native 事务,唯一关联实例沿 Kernel admin_delete;待启动、多实例及明细另有关联明确阻塞。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"需要将资料维护权限与流程管理员权限分别授予的 V2 应用及平台维护者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"消费同源 SDK/contracts/devkit 与提供 data.workflow-record-deletion@1.0.0 的 Server。",
|
|
19
|
+
"显式声明 recordDeletion 与资料 read/delete、维护能力,沿同一成员的数据范围执行。",
|
|
20
|
+
"未知提交先核原回执;只有专用回执不存在且原预览有效时,显式用原请求重试。"
|
|
21
|
+
],
|
|
22
|
+
"knownLimitations": [
|
|
23
|
+
"本批仅本地包,无 npm 发布;真实应用六组权限与正式本地部署验收仍待共享平台验证窗口。",
|
|
24
|
+
"owned 删除上限100条、深度8;多个关联实例、待启动命令及明细关联其他实例不支持自动删除。",
|
|
25
|
+
"预览有效期五分钟,过期后仍可恢复原回执;原 CSRF 绑定保留在既有512条身份缓存中,容量淘汰、退出或刷新后不保证恢复。页面不跨刷新保存原请求。",
|
|
26
|
+
"合成组件及隔离数据库证据不代表103条源流程完整业务验收。"
|
|
27
|
+
],
|
|
28
|
+
"issues": [],
|
|
29
|
+
"compatibility": {
|
|
30
|
+
"node": ">=24",
|
|
31
|
+
"platform": "data.workflow-record-deletion@1.0.0;复用既有 Native 与 Kernel 数据表及平台密钥,无新增初始化开关。未声明应用与1.x保持原行为。"
|
|
32
|
+
},
|
|
33
|
+
"sha256": "940ca30e5fa17c12f4e22f675879a02d5f316eee276108ff9ab8b6e000e167b1",
|
|
34
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.54.0"
|
|
35
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.54.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "业务动作模型的受控删除授权修正",
|
|
6
|
+
"summary": "显式开启资料维护删除的模型可以声明其 Native 删除范围能力,仍由受控入口执行删除。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"双编译器仅为非空 recordDeletion.delete 放行模型删除能力授予;普通创建、更新、删除和关闭维护入口的模型继续遵守原所有者约束。"
|
|
10
|
+
],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"由业务动作维护申请数据、同时需要独立资料删除权的 V2 应用。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"使用同源本地 SDK2.54.1/contracts2.59.1/devkit2.47.1及完整配套包,重新生成契约并运行公开应用检查。"
|
|
16
|
+
],
|
|
17
|
+
"knownLimitations": [
|
|
18
|
+
"受控删除仍限零个或唯一根关联实例、owned100条及深度8;待启动、多流程和明细其他关联保持阻塞。",
|
|
19
|
+
"预览五分钟;未知提交先恢复原回执。原 CSRF 缓存有界,退出、刷新或容量淘汰后不保证恢复。",
|
|
20
|
+
"本批不发布 npm,真实应用权限及正式部署验收仍待执行;不代表103条源流程业务已完成。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"platform": "data.workflow-record-deletion@1.0.0;普通 Native mutationOwner 授权边界保留,默认未声明不启用。"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "2e1de49c0dfe3b700f29e5a3bbb0e46f9923456878f8b9bece259fe26808d954",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.54.1"
|
|
29
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.55.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "具名事务当前办理人操作与范围校验",
|
|
6
|
+
"summary": "增加显式 actor-authority 事务条件,将当前办理人的角色、动作能力和精确范围在平台事务内绑定为同一有效成员,并保留原目标成员断言。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"具名业务动作可声明 roleAssertions.actorAuthority:true,自动派生 data.transaction-actor-authority@1.0.0。",
|
|
9
|
+
"共享 Schema、双编译器、ESM/CJS 纯规则与 Nest SDK 贯通严格有界的 anyOf 角色/范围条件。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要将当前办理人管理范围和关键业务写入一起提交的 V2 应用;省略新声明的应用沿用原语义。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"完整同源升级 SDK 与平台合同实现;确认目标能力后,在对应具名动作显式声明允许角色和 actorAuthority。",
|
|
17
|
+
"使用平台当前 actor、动作能力与同成员范围;业务归属通过同一 Native 事务的记录 revision/CAS 守卫冻结。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"本轮仅授权本机源码和同源 SDK 验证,未进行 npm 或学校生产发布。",
|
|
21
|
+
"新守卫需要配套平台运行时;平台单元、真实 PostgreSQL 并发以及应用角色/页面验收分别记录,SDK 检查不替代业务验收。",
|
|
22
|
+
"应用源码托管、完整功能迁移和性能验收继续按各应用台账处理。"
|
|
23
|
+
],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=22,维护工具链使用 Node.js 24",
|
|
26
|
+
"platform": "data.transaction-actor-authority@1.0.0;普通调用、事件和队列不支持新条件"
|
|
27
|
+
},
|
|
28
|
+
"issues": [],
|
|
29
|
+
"sha256": "1cd2fcb3281c735ad649a82112da7806635f7d016243fe7b5ba30d12be9ea90f",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.55.2"
|
|
31
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.55.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.55.3:认证公共投影与管理范围",
|
|
6
|
+
"summary": "登录用户公共字段与有权管理私有字段通过同一 Native 资源声明,公共基线例外由双编译器闭合证明。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"只读 dataPolicy.publicRead.fields 声明唯一公共业务字段,协商 data.authenticated-public-projection@1.0.0。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"保留直接 baseline unrestrictedRoleCodes 保护;拒绝公共字段畸形、私有字段或历史误开放及 canonical 篡改。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"需要在同一资源保留认证公共目录并按学院或负责人范围管理私有字段的 V2 应用。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"使用完整同源 SDK 与配套平台;显式声明只读公共字段,全部未列出字段及 audit.read 必须拒绝基线,重新执行 check 和真实角色验收。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"不开放匿名普通 Data API,不支持公共子表;发行和实际应用验收分别记录,本轮仅本机使用。"
|
|
21
|
+
],
|
|
22
|
+
"compatibility": {
|
|
23
|
+
"node": ">=24",
|
|
24
|
+
"platform": "native-4;需 data.authenticated-public-projection@1.0.0",
|
|
25
|
+
"v1": "V1 引擎与应用不变"
|
|
26
|
+
},
|
|
27
|
+
"issues": [
|
|
28
|
+
"PLT-031"
|
|
29
|
+
],
|
|
30
|
+
"sha256": "c4f158dfd785f22e7d47453d29bd6b47be2318d6aa10ddac91dea5c729f677c8",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.55.3"
|
|
32
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.55.4",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.55.4:生成管理视图的只读类型",
|
|
6
|
+
"summary": "公共 React perspectives 输入接受编译器生成的非空嵌套只读声明,运行时授权语义不变。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"RuntimePerspective 复用 DeepReadonly,修复 appPerspectives as const 不能直接传入 OpenXiangdaApplication 的类型错误。"
|
|
10
|
+
],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"声明非空管理读取 Perspective 的 V2 React 应用。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"安装完整同源 SDK,保留官方生成契约,重新执行 check 并验证真实页面。"
|
|
16
|
+
],
|
|
17
|
+
"knownLimitations": [
|
|
18
|
+
"类型验收不代替真实角色与行/字段范围验收;本轮仅本机分发,不发布 npm。"
|
|
19
|
+
],
|
|
20
|
+
"compatibility": {
|
|
21
|
+
"node": ">=24",
|
|
22
|
+
"platform": "native-4;无需新增平台协议",
|
|
23
|
+
"v1": "V1 引擎与应用不变"
|
|
24
|
+
},
|
|
25
|
+
"issues": [
|
|
26
|
+
"PLT-032"
|
|
27
|
+
],
|
|
28
|
+
"sha256": "da27687ca41f4d3d6dd0e728a2fcffff6c08a0b129f8d0959ce2407ca3e5c6fa",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.55.4"
|
|
30
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.56.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "审批支持持久自动完成期限",
|
|
6
|
+
"summary": "可选评价等节点可以在固定期限后自动完成,平台持久计时并显示实际规则与历史。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"审批声明completionDeadline及能力协商,拒绝必填输入和自定义同意处理器冲突。",
|
|
9
|
+
"公开任务期限状态、固定图规则及PC/手机截止时间提示,管理员配置保留代码规则。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要限时自动完成可选审批节点的V2应用。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级完整同源SDK并使用支持workflow.completion-deadline@1.0.0的Server。",
|
|
17
|
+
"由代码声明afterSeconds和approve,不需要打开额外功能开关。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"本轮仅本地分发,未发布npm、学校或生产。",
|
|
21
|
+
"自动完成整节点,不产生未处理人的同意票;补正/恢复任务继续人工处理。",
|
|
22
|
+
"30秒扫描可能有排队延迟;12次失败后保留人工处理,管理员重试入口后续实现。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "workflow.completion-deadline@1.0.0,正式SQL迁移及持久worker",
|
|
28
|
+
"v1": "V1应用不消费此声明"
|
|
29
|
+
},
|
|
30
|
+
"sha256": "dacaddf6a4b812e45256e8b42b4cef4ea0db767ee17fa85995ee7e437e2b574c",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.56.0"
|
|
32
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.57.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "审批任务支持字典选项与后续阶段空引用",
|
|
6
|
+
"summary": "任务中的资源引用按当前办理权限读取字典,后续才补填的单值引用可以在提交时为空。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"PC和手机任务选择器自动绑定当前任务、任务版本与资料修订,保留目标字典读取权限和行权限。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"审批办理选择字典不再误要求主体资料的普通CRUD更新权限。",
|
|
12
|
+
"工作流单值快照允许显式object/null,保持Native必填校验及多值数组形状。",
|
|
13
|
+
"可选vendor目录纳入只读后端构建输入,完整本地SDK归档无需回落到registry。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"使用action-owned资料、审批补填字典或本地SDK归档的V2应用开发者。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"升级完整同源SDK,并使用实现workflow task field source/query接口的Server。",
|
|
20
|
+
"使用标准任务表单会自动传递上下文;自定义表单按工作流文档提供两份当前修订。"
|
|
21
|
+
],
|
|
22
|
+
"knownLimitations": [
|
|
23
|
+
"本批仅用于本地分发与合成业务验收,未发布npm、学校或生产。",
|
|
24
|
+
"仅当前任务页面可见且可填写的根引用字段可以查询;子表引用字段继续不支持。",
|
|
25
|
+
"字段显隐和流转逻辑仍由应用代码确定,管理员不通过节点配置改写这些规则。"
|
|
26
|
+
],
|
|
27
|
+
"issues": [],
|
|
28
|
+
"compatibility": {
|
|
29
|
+
"node": ">=24",
|
|
30
|
+
"platform": "当前任务资源引用接口及Native读取授权/RLS",
|
|
31
|
+
"v1": "V1应用不消费新增V2任务接口"
|
|
32
|
+
},
|
|
33
|
+
"sha256": "7014a7421c5060105ecfd98f773703bdff704866e1f1892caaddd430acdd72f3",
|
|
34
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.57.0"
|
|
35
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "入口排队观察节奏与同源契约升级",
|
|
6
|
+
"summary": "尊重服务器入口排队查询间隔,并发行主线已评审的owned聚合容量及固定工作流阶段事务能力。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型可声明最高1000行的owned聚合容量,缺省500行、单子表500行与原子编辑边界不变。",
|
|
9
|
+
"固定且已协调的工作流阶段可显式启用一次阶段绑定的Native数据事务,并恢复原事务回执。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"入口身份读取不再把60秒服务端查询提示压缩为15秒,保留最低间隔、抖动、原截止、取消及权限拒绝边界。",
|
|
13
|
+
"CLI模板使用本次根SDK精确版本,保证新建应用与发行能力一致。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"启用入口等待的V2应用,以及使用新增可选owned容量或工作流阶段事务声明的应用。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"精确安装完整同源发行组合;新增契约需匹配平台能力。高并发应用在真实页面和隔离HTTP请求图中校准查询节奏。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"本次客户万人复测尚未执行。上轮已登录万人HTTP图30分钟客户端与数据对账通过,严格网关对账仍保留18条已dispatch缺行。",
|
|
23
|
+
"不自动重放业务写入,不扩大权限或刷新原截止;不证明集中SSO、万人同秒提交、浏览器渲染容量或硬件绝对上限。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"platform": "新增声明按目标平台能力协商;共享契约须消费同源版本",
|
|
29
|
+
"v1": "V1不消费本批V2运行时能力"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "f6d7b5a8d416ba728f598cd0e24680fb13ffab779a5ad568d306e02c0e77f5bf",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.2"
|
|
33
|
+
}
|