openxiangda 2.75.3 → 2.75.5
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/RichTextField.d.ts.map +1 -1
- package/dist/browser/components/platform-fields/RichTextField.js +24 -7
- package/dist/browser/components/platform-fields/RichTextField.js.map +1 -1
- package/documentation/getting-started.md +7 -7
- package/documentation/manifest.json +3 -3
- package/documentation/reference/mcp.md +10 -0
- package/package.json +33 -26
- 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.51.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.54.4.json +30 -0
- package/releases/2.54.6.json +30 -0
- package/releases/2.55.0.json +34 -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.55.5.json +30 -0
- package/releases/2.56.0.json +32 -0
- package/releases/2.57.0.json +35 -0
- package/releases/2.58.0.json +37 -0
- package/releases/2.58.1.json +31 -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.60.0.json +38 -0
- package/releases/2.60.2.json +31 -0
- package/releases/2.67.2.json +34 -0
- package/releases/2.7.0.json +37 -0
- package/releases/2.7.1.json +31 -0
- package/releases/2.75.5.json +39 -0
- package/releases/2.8.0.json +32 -0
- package/releases/2.8.1.json +30 -0
- package/releases/2.9.0.json +33 -0
- package/releases/2.9.1.json +31 -0
- package/releases/2.9.2.json +33 -0
- package/releases/2.9.3.json +31 -0
- package/releases/2.9.4.json +37 -0
- package/skills/manifest.json +1 -1
- package/skills/openxiangda-v2/SKILL.md +4 -4
- package/skills/openxiangda-v2/references/getting-started.md +7 -7
- package/skills/openxiangda-v2/references/mcp.md +10 -0
- package/releases/2.71.0.json +0 -38
- package/releases/2.75.3.json +0 -32
|
@@ -0,0 +1,28 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.47.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "任务主要操作与附件可访问性",
|
|
6
|
+
"summary": "退回重提按平台主要操作呈现,PC附件上传使用具备禁用和键盘语义的真实按钮。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"手机任务动作排序支持服务端标为主要操作的重新提交。",
|
|
10
|
+
"PC附件上传提供原生按钮、焦点环和禁用状态,避免键盘Enter由按钮与上传容器重复处理。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用标准任务页面或PC Field Kit附件/图片字段的OpenXiangda 2.0应用。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"按精确版本升级SDK;退回重提主要操作需要平台服务端提供正确descriptor。本批仅本地验证,不执行npm发布。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"流程资格、上传与下载协议沿平台现有能力;本批不扩大任务子表容量,也不代表完整学校流程迁移验收。"
|
|
20
|
+
],
|
|
21
|
+
"compatibility": {
|
|
22
|
+
"node": ">=22.12.0",
|
|
23
|
+
"platform": "OpenXiangda 2.0;不改变1.x运行时"
|
|
24
|
+
},
|
|
25
|
+
"issues": [],
|
|
26
|
+
"sha256": "c4fe0b7fa686f777d1ac4786c3caa0efb7efecb81e7cbc7a1c00220d70849051",
|
|
27
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.47.2"
|
|
28
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.47.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "任务条件材料首次显示的空值修复",
|
|
6
|
+
"summary": "任务根字段及子表首次显示未填写的附件或图片时,使用标准空数组完成保存和私有草稿编码。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"任务附件和图片控件未填写时统一编码为空数组,避免条件字段首次显示后因null违反Native值合同。",
|
|
10
|
+
"根字段和owned子行共用编码规则,保留子行身份、只读和隐藏字段提交边界。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用标准流程任务表单、条件附件或图片字段及任务私有草稿的OpenXiangda 2.0应用。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"按精确版本升级SDK及同批CLI;首次条件激活还需要平台Server配套省略本次空材料写入。本批仅供本地验证,不执行npm发布。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"上传及非空材料引用仍按已经保存的页面条件校验,需要先保存使字段生效。",
|
|
20
|
+
"不调整源流程子表容量,不代表学校完整业务迁移验收。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=22.12.0",
|
|
25
|
+
"platform": "OpenXiangda 2.0;不改变1.x运行时"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "508dede83d96b9a52a29535ce76d7f7cd1bfbfb95e48d04eb84015fe09d7b586",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.47.3"
|
|
29
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.47.4",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "办理页面过期后的操作刷新",
|
|
6
|
+
"summary": "任务操作凭证过期时保留禁用的服务器可见命令,提供保留输入的只读刷新入口。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"PC与手机长时间停留后不再无提示地丢失操作按钮,凭证到期及时显示刷新操作提示。",
|
|
10
|
+
"刷新沿原Surface读取保留未保存表单,并继续遵守上传、草稿和未知命令恢复锁。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用标准或可嵌入任务操作面板,且办理页面停留超过操作凭证有效期的OpenXiangda 2.0用户。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"按精确版本升级SDK和同批CLI,无数据库迁移;本批仅本地验证,不执行npm发布。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"刷新重新读取当前权限,不能恢复已经被撤销的资格,也不会自动重发未决命令。",
|
|
20
|
+
"完整业务流程及源容量验证仍单独实施。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=22.12.0",
|
|
25
|
+
"platform": "OpenXiangda 2.0;不改变1.x运行时"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "bc6f8e6a404a8dac770842abb7da4560837734e5840698bf103e0c6a3fbe62b9",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.47.4"
|
|
29
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.47.5",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "固定流程图的可读摘要与定位",
|
|
6
|
+
"summary": "条件卡和步骤卡直接呈现声明的判断变量与产出,长图首次打开保持可读比例,选中来源时定位目标。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"长图按实际缩放判断初始视口,避免节点较少但布局很长时文字过小。",
|
|
10
|
+
"节点摘要取自同版本条件路径与业务步骤输出,列表和画布均跟随外部选择,保留正交连线和固定拓扑。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用共享WorkflowDiagram的OpenXiangda 2.0应用和流程管理后台。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级精确SDK和同批CLI;重新构建消费该SDK的流程管理前端,无数据库迁移。本批仅本地制品验证,不执行npm发布。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"说明由已发布readability元数据提供,界面不推断或执行计算代码;缺失说明需开发者随新定义补充。",
|
|
20
|
+
"完整业务流程和容量边界需按应用单独验收。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=22.12.0",
|
|
25
|
+
"platform": "OpenXiangda 2.0同版本graph projection;不改变1.x运行时"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "7b144e22517c27499eb4763d106f65874675090d1b990703ab10dd4fd52fdfa0",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.47.5"
|
|
29
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.48.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "有界主子表容量与整单流程发起",
|
|
6
|
+
"summary": "标准流程可通过现有Field Kit填写并原子提交声明的主子表,任务办理和草稿共同支持源业务所需的50/350行规模。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"标准流程发起页支持声明子表;子行日期和零值沿字段编码,原命令保持整体提交与原结果恢复。",
|
|
9
|
+
"每表最多100行、父资源与任务页声明合计400行,完整替换保留旧行删除与新行意图。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"统一事务1000操作/2MiB、任务值1MiB和普通表单草稿2MiB预算;页面定义、状态及文件保持独立配额。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"使用OpenXiangda 2.0主子表、标准流程发起和任务办理的开发者与用户。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"先安装包含有界容量、标准主子表发起和正式授权增量迁移的匹配Server,再升级本批精确SDK/CLI并构建应用。",
|
|
19
|
+
"本任务仅本地打包及合成环境验证,不执行npm发布。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"一般child CRUD不提供跨所有写入者的父集合容量锁;标准整单提交与任务提交按各自受控事务验证。",
|
|
23
|
+
"最大附件组合仍受文件配额限制;本批容量能力不代表学校完整源流程通过运行验收。",
|
|
24
|
+
"产生大记录后应先停止新定义并处理在途;不能直接降级到旧49行runtime或截断数据。"
|
|
25
|
+
],
|
|
26
|
+
"issues": [],
|
|
27
|
+
"compatibility": {
|
|
28
|
+
"node": ">=22.12.0",
|
|
29
|
+
"platform": "匹配的Native/BusinessProcess/Workflow/FormDraft运行时及增量SQL;1.x不消费这些契约"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "ea24a3f478a5fdfd7f6907ba0693f151d98456af554c7370cdb169e492e7400c",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.48.0"
|
|
33
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.48.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "大子表分页与整表校验",
|
|
6
|
+
"summary": "PC与手机主子表每页渲染十行,保留完整输入、草稿、排序和整单提交;校验覆盖全部行。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"减少大子表同时挂载的编辑控件;未显示行继续复用标准字段规则校验,任务完成的错误定位到对应页。",
|
|
10
|
+
"跨页移动使用绝对行序号,上传和待重试文件未处理时保留当前页。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用V2标准主子表、流程发起或任务办理页面的用户。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级精确SDK/CLI并重新构建应用;本修正不引入服务端迁移或数据格式变更。",
|
|
17
|
+
"本任务仅本地包消费与合成验证,不执行npm发布。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"分页是渲染边界,数据和事务仍遵守原先每表100行、声明合计400行等预算。",
|
|
21
|
+
"最大附件组合与学校完整源流程运行验收仍单独验证。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "沿用2.48.0匹配平台;1.x不消费此组件"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "ba545c3aadbbc7a8b4b31de91b2257dd1600df59c20e05e0ec452c0bf07362b0",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.48.1"
|
|
30
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.48.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "子表输入与整表提交校验",
|
|
6
|
+
"summary": "保留子表分页的全部校验,在提交时定位离页错误,输入时稳定停留在当前页。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"父级子表完整校验只在显式校验或提交时执行,避免逐键扫描全部行并跳转至尚未填写的页;当前页字段仍即时反馈。"
|
|
10
|
+
],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"使用V2标准主子表、流程发起或任务办理页面的用户。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"升级精确SDK/CLI并重新构建应用;本修正不引入服务端迁移或数据格式变更。",
|
|
16
|
+
"本任务仅本地包消费与合成验证,不执行npm发布。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"分页是渲染边界,数据和事务仍遵守原先每表100行、声明合计400行等预算。",
|
|
20
|
+
"最大附件组合与学校完整源流程运行验收仍单独验证。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"platform": "沿用2.48.0匹配平台;1.x不消费此组件"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "bfc22a1f10ca53c3d5146d4e0b797363afa4f0ae78dda80b0a9724e74d0bc4f9",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.48.2"
|
|
29
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.48.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "审批节点的显式空人员策略",
|
|
6
|
+
"summary": "应用可按节点声明真实空审批人时阻塞或跳过,并在固定流程图和历史中展示实际跳过记录。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"审批 emptyPolicy 默认 block;显式 skip 仅接受受支持来源成功解析的真实零人结果,能力协商要求 workflow.approval-empty-policy@1.0.0。",
|
|
9
|
+
"冻结空人策略并显示已跳过;管理员仍只能修改代码允许的节点参数,不能更改空人策略或流程拓扑。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"新建标准申请中已展示的人员多选初始化为显式空数组;已有记录和接口漏传字段保持原语义。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"需要区分无人跳过与最终必审阻塞的 V2 工作流应用。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"同时升级服务端能力与精确 SDK/CLI 合同,重新构建应用;不需要数据库迁移。",
|
|
19
|
+
"本轮使用本地封装包进行合成验证,未执行 npm 发布。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"skip 支持 fixed_users、input_users、form_field_users、app_role、app_role_in_scope;其他来源暂不支持。",
|
|
23
|
+
"缺失/null、非法账号、解析失败和退回补正不能自动跳过;完整源业务验收单独进行。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"platform": "要求 workflow.approval-empty-policy@1.0.0;1.x 不消费此能力"
|
|
29
|
+
},
|
|
30
|
+
"sha256": "318a066e3384b6dd0441d7783fc3baee8d526b833e27649ff5ae33e6805e62d7",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.48.3"
|
|
32
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.48.4",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "限定职责选人的字段与流程合同",
|
|
6
|
+
"summary": "定义人员候选职责、记录范围和固定流程字段绑定,编译时拒绝来源漂移和范围绕过。此版本用于后续运行时接入,尚未开放该平台能力。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"user.single/user.multiple 的 userCandidates 引用同包职责与可选范围,schema、Surface和纯编译器共同校验。",
|
|
9
|
+
"form_field_users 的 candidateField 精确引用主体字段与事实投影,禁止重复来源配置、嵌套路径绕过和任务同时修改范围与选择。",
|
|
10
|
+
"使用该声明自动要求 data.user-candidates@1.0.0;未支持的平台必须拒绝部署。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"需要按职责和已保存业务范围选择审批人的 V2 应用开发者及平台维护者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"本轮只固定本地合同包供平台接入,不执行 npm 发布或生产部署。",
|
|
18
|
+
"应用须等待 Native、Workflow、SDK及双端组件验证完成且平台广告能力后再采用声明。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"尚无公开候选接口或完整运行时约束;仅有编译检查不能证明选人或流程验收完成。",
|
|
22
|
+
"首版任务只支持主体候选字段,可写子表候选字段明确拒绝;新建不能提交非空的记录范围选人。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "目标须支持 data.user-candidates@1.0.0;1.x 不消费新合同"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "2795353dc826b385cf6bef43883266fb9727b99e0ce2c9eaa7c12369e121fbc7",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.48.4"
|
|
31
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "表单与审批任务的限定职责选人",
|
|
6
|
+
"summary": "为限定职责的人员字段提供 SDK 查询和电脑、手机选择器,支持分页、已选复核、失效提示与当前任务版本绑定。配套平台负责候选授权、保存及进入审批节点时的再次核验。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"Native 表单和当前审批任务可通过正式 SDK 查询声明中的候选职责,保留记录修订与任务版本边界。",
|
|
9
|
+
"电脑和手机 Field Kit 支持搜索、分页、跨页选择、清空、取消、确认前复核及失效历史值显示。",
|
|
10
|
+
"普通 CRUD、发起页、任务补填和资料修正页传递同一候选上下文,职责引用展示受限字段来源。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"补齐候选查询与返回的 JSON Schema,查询失败或缺少上下文时明确报错,过时响应不覆盖当前选择。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"使用按职责或已保存业务范围选择审批人的 V2 应用开发者、流程管理员和办理人员。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"本轮版本封存用于本地 SDK 与平台联合验证,不执行 npm 发布或生产部署。",
|
|
20
|
+
"目标平台须支持 data.user-candidates@1.0.0;在 user.single/user.multiple 字段上声明 userCandidates,流程通过 candidateField 引用该字段。",
|
|
21
|
+
"升级应用的精确依赖并重新生成、检查和测试部署;按真实角色验证候选范围、事务保存、任务补填及下游派单。"
|
|
22
|
+
],
|
|
23
|
+
"knownLimitations": [
|
|
24
|
+
"首版任务仅支持主体候选字段;可写子表候选字段仍明确拒绝。",
|
|
25
|
+
"使用记录字段作为范围时,新建不能选择非空人员;须先保存范围,后续任务按该保存值选人。",
|
|
26
|
+
"源码检查和合成组件验收不代表学校流程或完整应用运行验收完成。"
|
|
27
|
+
],
|
|
28
|
+
"issues": [],
|
|
29
|
+
"compatibility": {
|
|
30
|
+
"node": ">=24",
|
|
31
|
+
"platform": "data.user-candidates@1.0.0;稳定 1.x 和普通人员字段不消费新候选合同"
|
|
32
|
+
},
|
|
33
|
+
"sha256": "618a1e0ea1c9292de4f9a7120905fb5e11453e674e224cf46f57b34bb1316491",
|
|
34
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.0"
|
|
35
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "候选职责的成员范围维护",
|
|
6
|
+
"summary": "成员管理识别人员候选字段声明的范围,支持当前与在办流程的字段版本,并正确处理数据策略的逐规则适用性。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"管理目录提供 candidateFields 引用,可追溯候选角色对应的资源、字段、数据修订与操作。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"没有 CRUD 范围策略的审批人职责也能配置声明中的范围。",
|
|
12
|
+
"SDK 维度筛选按逐策略规则及候选职责判断,保留无限制角色和 OR 语义。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"通过角色与范围维护审批候选人的 V2 应用开发者和管理员。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"本轮仅封装本地测试包,不执行 npm 发布。",
|
|
19
|
+
"配套平台须包含候选范围适用性修复;更新精确依赖后验证范围维护、候选选择与任务办理。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"候选字段不会赋予额外 CRUD、菜单或应用管理权限。",
|
|
23
|
+
"学校完整流程验收仍独立于合成平台验证。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"platform": "V2 候选范围适用性修复;不影响稳定 1.x"
|
|
29
|
+
},
|
|
30
|
+
"sha256": "0e629fd587327d3cea452a3f021c7dc5a7bc5dc40ae32b17b3d10f86de0aa3fd",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.1"
|
|
32
|
+
}
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.10",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "发起人审批策略与真实流程说明",
|
|
6
|
+
"summary": "增加代码声明的发起人自动同意契约、能力协商和固定流程图说明,保持审批配置的有限修改边界。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"审批节点可声明 initiatorApprovalPolicy,默认 manual;auto_approve 只面向原解析产生的当前发起人直接席位。",
|
|
9
|
+
"节点配置和固定流程图显示代码拥有的策略,执行图可读取持久化的自动审批证据。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"配置校验拒绝自动同意与强制同意意见、补填页面或可写字段的组合。",
|
|
13
|
+
"同步托管媒体文档到随包 Skill 参考,保持开发资料同源。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"重建多人审批、发起人与审批人重合业务以及维护固定流程配置的开发者和管理员。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"升级完整根包组合,并使用支持 workflow.initiator-approval-policy@1.0.0 的配套服务端。",
|
|
20
|
+
"只为没有必填业务输入的审批节点显式声明 auto_approve;需要补选人员、补材料等节点继续使用 manual。"
|
|
21
|
+
],
|
|
22
|
+
"knownLimitations": [
|
|
23
|
+
"代理、转交、加签、管理员重分配和退回补正保持人工办理,不能用自动同意替代业务输入。",
|
|
24
|
+
"不代表已精确复现宜搭 originatorMerge 的全部运行效果;真实源流程仍需逐条验收。",
|
|
25
|
+
"本轮只进行本地配套分发,不发布 npm 或执行学校生产迁移。"
|
|
26
|
+
],
|
|
27
|
+
"issues": [],
|
|
28
|
+
"compatibility": {
|
|
29
|
+
"node": ">=24",
|
|
30
|
+
"platform": "新增显式能力协商;只有声明该策略的 V2 应用需要配套 Workflow 实现,默认人工和 1.x 保持原行为。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "b20657ae94bdda668654996d5f5f526ce3bda95df005327c959764d143ae23e4",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.10"
|
|
34
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.11",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "保留原生 Nest 业务拒绝说明",
|
|
6
|
+
"summary": "修复浏览器 SDK 丢失没有 code 字段的原生 Nest HTTP 拒绝文案,继续保留结构化错误与原请求恢复边界。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"非成功 HTTP JSON 对象即使没有 code,也保留后端的中文 4xx message、data、retryable 和请求诊断。",
|
|
10
|
+
"根包与 CLI 打包模板的精确依赖按既有耦合规则同步版本化。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用可选 Nest 后端业务动作、需要显示明确冲突或权限拒绝原因的 V2 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"升级完整根包发行并核对项目锁文件;既有生成契约与平台配置不需因本修复改变。",
|
|
17
|
+
"应用按结构化 code/status 和提交阶段判断恢复,不通过解析中文文案自动重试写入。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"仅支持既有合法字符串 message;非 JSON、primitive 和数组错误响应继续显示 HTTP fallback。",
|
|
21
|
+
"本轮仅本机完整配套分发,不代表 npm 发布、生产部署或应用全部功能验收。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "无新增平台契约或权限要求;继续使用当前项目匹配的完整校验器发行。V1 引擎保持原行为。"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "bebca7dfc7577833fe7f79e9bf7e14fa73681c4bf64eb564882b025e11a7d8b7",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.11"
|
|
30
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.12",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "显式读取本人业务联系电话",
|
|
6
|
+
"summary": "本人报名等具名业务动作可声明只读电话投影,编译器派生独立平台能力,默认身份和其他人员查询保持原投影。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"current-initiator 目录支持显式声明 phone,并将可空且最多80字符的电话纳入 snapshotRevision。",
|
|
9
|
+
"受管 backend-plan 命令使用同一本人投影规则;两个编译器按实际声明派生 directory.current-initiator-phone 1.0.0。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要在本人报名或联系业务中展示平台账号只读电话的 V2 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"安装完整同源根包发行,并先配套实现该能力的 Server;由编译器生成契约和要求,不手改摘要。",
|
|
17
|
+
"业务按原规则处理缺失电话,提交重新核对正式目录修订,不能接受浏览器身份快照。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"默认 SubjectProfile、人员搜索和 selected-user 不查询或返回电话。",
|
|
21
|
+
"不提供手机号查人或电话修改;本轮仅本机配套发行,不代表 npm 或生产部署。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "新 phone 声明需要 directory.current-initiator-phone 1.0.0 及同源完整校验器。既有不声明 phone 的目录行为和 V1 引擎不变。"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "e9f3ee1ec0e86f6cec12288bc02d64dc6af1db8e579ff336e0feef936e4842b4",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.12"
|
|
30
|
+
}
|
|
@@ -0,0 +1,29 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.13",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "流程详情准确显示当前等待人员",
|
|
6
|
+
"summary": "PC和手机的在办流程顶部使用平台当前有效席位显示等待人员,历史仍保留完整进入名单和办理记录。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"会签中已经自动或人工同意的人不再显示为等待;依次审批后续pending席位、已转交或取消的人也不计入当前等待。",
|
|
10
|
+
"按稳定visit key匹配当前节点,避免同一节点重复进入时混用历史名单;缺少明确状态时只显示节点。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用V2标准PC或手机流程详情页的应用及审批人员。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"安装同源本地SDK组合并重新构建用户端;复用既有Workflow详情协议。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"本轮只做本地包消费与验证,没有npm发布或生产部署。",
|
|
20
|
+
"不改变流程人员解析、权限、执行、数据或完整历史;学校103条源流程仍需逐项验收。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"platform": "复用现有WorkflowTimelineFlowItem.assignees.status和display entry key;V1引擎不变。"
|
|
26
|
+
},
|
|
27
|
+
"sha256": "29838892d286d510a2cff475f4ae727b7fc73e11e1e21f479274d1dbc50d979c",
|
|
28
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.13"
|
|
29
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.49.14",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "流程办理校验意见并保留明确拒绝的输入",
|
|
6
|
+
"summary": "PC与手机的标准操作表单按平台Schema核对意见和原因,明确拒绝后保留同一有效操作的输入供用户重新确认。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"操作表单不再忽略string的minLength、maxLength和pattern;必填文字不能仅为空格。",
|
|
10
|
+
"明确拒绝后,同一实例、任务版本、流程序列和操作签名仍有效时保持对话框与输入;当前权限和版本变化继续阻断旧操作。",
|
|
11
|
+
"意见、原因及转交本人拒绝提供可读提示,未知结果仍锁原请求并恢复原回执。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用V2标准PC或手机审批操作面板的应用与审批人员。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"安装同源本地SDK组合并重新构建应用用户端;平台Server同时提供原因非空白Schema与事务前校验。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"本轮只消费本地密封包,没有npm发布或生产部署。",
|
|
21
|
+
"不改变流程拓扑、人员资格、节点字段权限或原命令协议;完整源业务验收继续独立记录。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "复用WorkflowSurface操作Schema及现有token/CAS/回执合同;原因校验与Server同步,V1引擎不变。"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "d3dcf657d0a5ebc50c861a2c74c47b1ee79c3de91baa3ed32d5e779ae201c2bf",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.49.14"
|
|
30
|
+
}
|
|
@@ -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
|
+
}
|