openxiangda 2.59.2 → 2.59.3-http.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/browser/components/platform-fields/SignatureField.d.ts.map +1 -1
- package/dist/browser/components/platform-fields/SignatureField.js +2 -4
- package/dist/browser/components/platform-fields/SignatureField.js.map +1 -1
- package/dist/browser/sha256.d.ts +3 -0
- package/dist/browser/sha256.d.ts.map +1 -0
- package/dist/browser/sha256.js +10 -0
- package/dist/browser/sha256.js.map +1 -0
- package/dist/browser/workflow-task-command-recovery.d.ts.map +1 -1
- package/dist/browser/workflow-task-command-recovery.js +2 -2
- package/dist/browser/workflow-task-command-recovery.js.map +1 -1
- package/documentation/getting-started.md +7 -7
- package/documentation/manifest.json +2 -2
- package/package.json +17 -20
- package/releases/2.0.0.json +50 -0
- package/releases/2.0.1.json +39 -0
- package/releases/2.1.0.json +44 -0
- package/releases/2.1.1.json +48 -0
- package/releases/2.10.0.json +42 -0
- package/releases/2.11.0.json +41 -0
- package/releases/2.12.0.json +38 -0
- package/releases/2.13.0.json +41 -0
- package/releases/2.13.1.json +33 -0
- package/releases/2.13.2.json +31 -0
- package/releases/2.14.0.json +41 -0
- package/releases/2.15.0.json +40 -0
- package/releases/2.16.0.json +41 -0
- package/releases/2.17.0.json +39 -0
- package/releases/2.17.1.json +34 -0
- package/releases/2.18.0.json +37 -0
- package/releases/2.18.1.json +31 -0
- package/releases/2.18.10.json +29 -0
- package/releases/2.18.2.json +30 -0
- package/releases/2.18.3.json +30 -0
- package/releases/2.18.9.json +37 -0
- package/releases/2.19.0.json +38 -0
- package/releases/2.2.0.json +48 -0
- package/releases/2.2.1.json +35 -0
- package/releases/2.2.2.json +34 -0
- package/releases/2.20.0.json +36 -0
- package/releases/2.20.1.json +30 -0
- package/releases/2.20.4.json +30 -0
- package/releases/2.21.0.json +35 -0
- package/releases/2.21.1.json +36 -0
- package/releases/2.21.2.json +34 -0
- package/releases/2.21.3.json +31 -0
- package/releases/2.21.4.json +31 -0
- package/releases/2.22.0.json +35 -0
- package/releases/2.22.1.json +32 -0
- package/releases/2.22.2.json +35 -0
- package/releases/2.22.3.json +32 -0
- package/releases/2.22.4.json +33 -0
- package/releases/2.22.5.json +31 -0
- package/releases/2.22.6.json +29 -0
- package/releases/2.22.7.json +29 -0
- package/releases/2.23.0.json +34 -0
- package/releases/2.24.0.json +33 -0
- package/releases/2.24.1.json +33 -0
- package/releases/2.24.2.json +31 -0
- package/releases/2.24.3.json +33 -0
- package/releases/2.25.0.json +31 -0
- package/releases/2.25.1.json +33 -0
- package/releases/2.25.2.json +32 -0
- package/releases/2.25.3.json +32 -0
- package/releases/2.26.0.json +41 -0
- package/releases/2.27.0.json +38 -0
- package/releases/2.28.0.json +37 -0
- package/releases/2.28.1.json +34 -0
- package/releases/2.29.0.json +37 -0
- package/releases/2.29.1.json +34 -0
- package/releases/2.29.2.json +32 -0
- package/releases/2.3.0.json +37 -0
- package/releases/2.30.0.json +34 -0
- package/releases/2.31.0.json +39 -0
- package/releases/2.31.1.json +38 -0
- package/releases/2.31.2.json +34 -0
- package/releases/2.31.3.json +32 -0
- package/releases/2.31.4.json +33 -0
- package/releases/2.31.5.json +33 -0
- package/releases/2.31.6.json +29 -0
- package/releases/2.31.7.json +29 -0
- package/releases/2.31.8.json +33 -0
- package/releases/2.31.9.json +33 -0
- package/releases/2.32.0.json +38 -0
- package/releases/2.33.0.json +33 -0
- package/releases/2.34.0.json +38 -0
- package/releases/2.34.1.json +34 -0
- package/releases/2.34.2.json +36 -0
- package/releases/2.34.3.json +35 -0
- package/releases/2.35.0.json +42 -0
- package/releases/2.35.1.json +43 -0
- package/releases/2.35.2.json +45 -0
- package/releases/2.35.3.json +46 -0
- package/releases/2.36.0.json +38 -0
- package/releases/2.36.1.json +33 -0
- package/releases/2.37.0.json +39 -0
- package/releases/2.37.1.json +33 -0
- package/releases/2.37.2.json +31 -0
- package/releases/2.38.0.json +40 -0
- package/releases/2.39.0.json +37 -0
- package/releases/2.39.1.json +32 -0
- package/releases/2.4.0.json +37 -0
- package/releases/2.4.1.json +35 -0
- package/releases/2.40.0.json +38 -0
- package/releases/2.40.1.json +30 -0
- package/releases/2.41.0.json +39 -0
- package/releases/2.41.1.json +33 -0
- package/releases/2.41.2.json +34 -0
- package/releases/2.42.0.json +36 -0
- package/releases/2.43.0.json +38 -0
- package/releases/2.44.0.json +36 -0
- package/releases/2.44.1.json +33 -0
- package/releases/2.45.0.json +35 -0
- package/releases/2.46.0.json +35 -0
- package/releases/2.46.1.json +30 -0
- package/releases/2.46.2.json +29 -0
- package/releases/2.46.3.json +30 -0
- package/releases/2.47.0.json +34 -0
- package/releases/2.47.1.json +31 -0
- package/releases/2.47.2.json +28 -0
- package/releases/2.47.3.json +29 -0
- package/releases/2.47.4.json +29 -0
- package/releases/2.47.5.json +29 -0
- package/releases/2.48.0.json +33 -0
- package/releases/2.48.1.json +30 -0
- package/releases/2.48.2.json +29 -0
- package/releases/2.48.3.json +32 -0
- package/releases/2.48.4.json +31 -0
- package/releases/2.49.0.json +35 -0
- package/releases/2.49.1.json +32 -0
- package/releases/2.49.10.json +34 -0
- package/releases/2.49.11.json +30 -0
- package/releases/2.49.12.json +30 -0
- package/releases/2.49.13.json +29 -0
- package/releases/2.49.14.json +30 -0
- package/releases/2.49.2.json +31 -0
- package/releases/2.49.3.json +31 -0
- package/releases/2.49.4.json +30 -0
- package/releases/2.49.5.json +31 -0
- package/releases/2.49.6.json +30 -0
- package/releases/2.49.8.json +33 -0
- package/releases/2.49.9.json +35 -0
- package/releases/2.5.0.json +37 -0
- package/releases/2.50.0.json +32 -0
- package/releases/2.52.0.json +34 -0
- package/releases/2.53.0.json +34 -0
- package/releases/2.54.0.json +35 -0
- package/releases/2.54.1.json +29 -0
- package/releases/2.55.2.json +31 -0
- package/releases/2.55.3.json +32 -0
- package/releases/2.55.4.json +30 -0
- package/releases/2.56.0.json +32 -0
- package/releases/2.57.0.json +35 -0
- package/releases/2.59.3.json +36 -0
- package/releases/2.59.4.json +38 -0
- package/releases/2.59.5.json +40 -0
- package/releases/2.59.6.json +30 -0
- package/releases/2.59.7.json +32 -0
- package/releases/2.6.0.json +37 -0
- package/releases/2.7.0.json +37 -0
- package/releases/2.7.1.json +31 -0
- package/releases/2.8.0.json +32 -0
- package/releases/2.8.1.json +30 -0
- package/releases/2.9.0.json +33 -0
- package/releases/2.9.1.json +31 -0
- package/releases/2.9.2.json +33 -0
- package/releases/2.9.3.json +31 -0
- package/releases/2.9.4.json +37 -0
- package/skills/manifest.json +1 -1
- package/skills/openxiangda-v2/SKILL.md +4 -4
- package/skills/openxiangda-v2/references/getting-started.md +7 -7
- package/releases/2.55.1.json +0 -32
- package/releases/2.55.6.json +0 -32
- package/releases/2.57.1.json +0 -31
- package/releases/2.59.0.json +0 -36
- package/releases/2.59.1.json +0 -37
|
@@ -0,0 +1,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,36 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "开发者AI应用自助操作与主线工具组合",
|
|
6
|
+
"summary": "让AI沿用当前应用权限直接诊断事件、复用加密环境凭据、配置通知和恢复指定投递;发行同源主线已评审的流程及编译契约。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"admin operations和MCP application_operations发现20项有界操作;admin execute及application_operation直接执行,必须明确环境,密钥仅返回元信息。",
|
|
9
|
+
"角色审批可按固定代码步骤或事实的选人结果取当前有效角色候选;平台必须提供workflow.role-input-selection能力,缺失时拒绝新声明。",
|
|
10
|
+
"流程表单支持已加载固定子表行及按原Native资源授权读取材料;流程图支持展开已声明代码逻辑说明。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"当前能力目录完整合法闭包不再受旧64项上限误拒绝;未知代码、重复项及制品绑定仍拒绝。",
|
|
14
|
+
"补正可编辑未参与流转事实投影的一层owned子表;固定子表条件隐藏采用当前表单值。",
|
|
15
|
+
"流程画布就绪后才开放导航,用户导航不再被迟到初始化覆盖;大型AppSpec支持512文件并保留原字节界限。"
|
|
16
|
+
],
|
|
17
|
+
"affectedUsers": [
|
|
18
|
+
"使用V2开发者CLI/MCP进行应用运维,或使用本批流程/编译增强的应用。稳定V1独立维护。"
|
|
19
|
+
],
|
|
20
|
+
"upgradeSteps": [
|
|
21
|
+
"精确更新完整工具组合,刷新工作区Skill和AGENTS平台区块并重启MCP。先读docs application-operations及admin operations --json。",
|
|
22
|
+
"共享校验器须与平台安装的openxiangda-contracts 2.71.0配对;已有生产应用保持原不可变版本,升级工具不代表重新部署业务。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"沿用当前应用管理授权;首次账号授权、权限委托和外部身份目录维护仍由原owner处理。旧平台缺少接口时明确拒绝,不使用SQL或保护绕过。",
|
|
26
|
+
"通道健康成功不证明实际老师收件或已读。恢复只处理指定原投递,不自动导入、重建业务、批量重发历史通知或读取密钥明文。"
|
|
27
|
+
],
|
|
28
|
+
"issues": [],
|
|
29
|
+
"compatibility": {
|
|
30
|
+
"node": ">=24",
|
|
31
|
+
"platform": "共享纯校验器同源配对;新增角色选人声明要求workflow.role-input-selection@1.0.0",
|
|
32
|
+
"v1": "V1不消费本批V2契约或运行时"
|
|
33
|
+
},
|
|
34
|
+
"sha256": "b09fb5780d5ceea6c72a61c174952039396debc774d9b4249aef79794308bb72",
|
|
35
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.3"
|
|
36
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.4",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "开发者AI应用自助操作与主线工具组合",
|
|
6
|
+
"summary": "让AI沿用当前应用权限直接诊断事件、复用加密环境凭据、配置通知和恢复指定投递;发行同源主线已评审的流程及编译契约。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"admin operations和MCP application_operations发现20项有界操作;admin execute及application_operation直接执行,必须明确环境,密钥仅返回元信息。",
|
|
9
|
+
"角色审批可按固定代码步骤或事实的选人结果取当前有效角色候选;平台必须提供workflow.role-input-selection能力,缺失时拒绝新声明。",
|
|
10
|
+
"流程表单支持已加载固定子表行及按原Native资源授权读取材料;流程图支持展开已声明代码逻辑说明。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"当前能力目录完整合法闭包不再受旧64项上限误拒绝;未知代码、重复项及制品绑定仍拒绝。",
|
|
14
|
+
"补正可编辑未参与流转事实投影的一层owned子表;固定子表条件隐藏采用当前表单值。",
|
|
15
|
+
"流程画布就绪后才开放导航,用户导航不再被迟到初始化覆盖;大型AppSpec支持512文件并保留原字节界限。",
|
|
16
|
+
"流程提交遵循当前声明的隐藏字段保留或清空策略,并保留提交字段白名单。",
|
|
17
|
+
"冻结发行允许权威主线后续前进;源提交必须仍在主线,制品及参考应用证据必须保持原样。"
|
|
18
|
+
],
|
|
19
|
+
"affectedUsers": [
|
|
20
|
+
"使用V2开发者CLI/MCP进行应用运维,或使用本批流程/编译增强的应用。稳定V1独立维护。"
|
|
21
|
+
],
|
|
22
|
+
"upgradeSteps": [
|
|
23
|
+
"精确更新完整工具组合,刷新工作区Skill和AGENTS平台区块并重启MCP。先读docs application-operations及admin operations --json。",
|
|
24
|
+
"共享校验器须与平台安装的openxiangda-contracts 2.71.0配对;已有生产应用保持原不可变版本,升级工具不代表重新部署业务。"
|
|
25
|
+
],
|
|
26
|
+
"knownLimitations": [
|
|
27
|
+
"沿用当前应用管理授权;首次账号授权、权限委托和外部身份目录维护仍由原owner处理。旧平台缺少接口时明确拒绝,不使用SQL或保护绕过。",
|
|
28
|
+
"通道健康成功不证明实际老师收件或已读。恢复只处理指定原投递,不自动导入、重建业务、批量重发历史通知或读取密钥明文。"
|
|
29
|
+
],
|
|
30
|
+
"issues": [],
|
|
31
|
+
"compatibility": {
|
|
32
|
+
"node": ">=24",
|
|
33
|
+
"platform": "共享纯校验器同源配对;新增角色选人声明要求workflow.role-input-selection@1.0.0",
|
|
34
|
+
"v1": "V1不消费本批V2契约或运行时"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "24320b39c5220c3acaf513b68532629801d3fc90f70f65659efcc69e1c7d616c",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.4"
|
|
38
|
+
}
|
|
@@ -0,0 +1,40 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.5",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "开发者AI应用自助操作与主线工具组合",
|
|
6
|
+
"summary": "让AI沿用当前应用权限直接诊断事件、复用加密环境凭据、配置通知和恢复指定投递;发行同源主线已评审的流程及编译契约。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"admin operations和MCP application_operations发现20项有界操作;admin execute及application_operation直接执行,必须明确环境,密钥仅返回元信息。",
|
|
9
|
+
"角色审批可按固定代码步骤或事实的选人结果取当前有效角色候选;平台必须提供workflow.role-input-selection能力,缺失时拒绝新声明。",
|
|
10
|
+
"流程表单支持已加载固定子表行及按原Native资源授权读取材料;流程图支持展开已声明代码逻辑说明。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"当前能力目录完整合法闭包不再受旧64项上限误拒绝;未知代码、重复项及制品绑定仍拒绝。",
|
|
14
|
+
"补正可编辑未参与流转事实投影的一层owned子表;固定子表条件隐藏采用当前表单值。",
|
|
15
|
+
"流程画布就绪后才开放导航,用户导航不再被迟到初始化覆盖;大型AppSpec支持512文件并保留原字节界限。",
|
|
16
|
+
"流程提交遵循当前声明的隐藏字段保留或清空策略,并保留提交字段白名单。",
|
|
17
|
+
"冻结发行允许权威主线后续前进;源提交必须仍在主线,制品及参考应用证据必须保持原样。",
|
|
18
|
+
"流程变量叶路径继承已声明父变量的显示标签;路径、条件和单位事实保持。",
|
|
19
|
+
"冻结manifest在planned回执建立前即可验证主线祖先关系;缺失或损坏制品拒绝,实际验证门禁仍必需。"
|
|
20
|
+
],
|
|
21
|
+
"affectedUsers": [
|
|
22
|
+
"使用V2开发者CLI/MCP进行应用运维,或使用本批流程/编译增强的应用。稳定V1独立维护。"
|
|
23
|
+
],
|
|
24
|
+
"upgradeSteps": [
|
|
25
|
+
"精确更新完整工具组合,刷新工作区Skill和AGENTS平台区块并重启MCP。先读docs application-operations及admin operations --json。",
|
|
26
|
+
"共享校验器须与平台安装的openxiangda-contracts 2.71.1配对;已有生产应用保持原不可变版本,升级工具不代表重新部署业务。"
|
|
27
|
+
],
|
|
28
|
+
"knownLimitations": [
|
|
29
|
+
"沿用当前应用管理授权;首次账号授权、权限委托和外部身份目录维护仍由原owner处理。旧平台缺少接口时明确拒绝,不使用SQL或保护绕过。",
|
|
30
|
+
"通道健康成功不证明实际老师收件或已读。恢复只处理指定原投递,不自动导入、重建业务、批量重发历史通知或读取密钥明文。"
|
|
31
|
+
],
|
|
32
|
+
"issues": [],
|
|
33
|
+
"compatibility": {
|
|
34
|
+
"node": ">=24",
|
|
35
|
+
"platform": "共享纯校验器同源配对;新增角色选人声明要求workflow.role-input-selection@1.0.0",
|
|
36
|
+
"v1": "V1不消费本批V2契约或运行时"
|
|
37
|
+
},
|
|
38
|
+
"sha256": "a50ff28ce680ae7ec080219eb0e010ba087b3915c65582a13578ba3b9a7833b7",
|
|
39
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.5"
|
|
40
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.6",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "配置容量预检与共享预算对齐",
|
|
6
|
+
"summary": "修复多流程应用部署预检使用旧配置预算的问题,兼容旧4 MiB和新8 MiB声明,保留能力协商、完整编译与总请求限制。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"配置兼容性能力声明接受已支持的4/8 MiB预算,其他上限和错误类型继续拒绝。",
|
|
10
|
+
"请求Schema与编译器共用配置预算;浏览器Schema只依赖纯常量,不引入Node加密模块。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"在V2平台部署或检查较大多流程应用的开发者;旧小配置与V1不受影响。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"消费精确配套工具组合,核验平台与工具的共享编译器摘要一致;本批先本地验证,不自动发布或激活生产应用。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"配置8 MiB、契约8 MiB仍受总请求10 MiB限制,任务页与JSON预算保持。",
|
|
20
|
+
"较大配置仍要求平台支持application.extended-configuration-bytes能力,旧站点缺失时在上传前拒绝。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"platform": "共享编译器同源配对;较大配置要求application.extended-configuration-bytes@1.0.0",
|
|
26
|
+
"v1": "V1不消费本批V2契约"
|
|
27
|
+
},
|
|
28
|
+
"sha256": "704919409c19828e4fc3b247f8967b50114e443c79ad5decd837fa77efcaa985",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.6"
|
|
30
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.7",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "多流程源码容量与自动抄送预算",
|
|
6
|
+
"summary": "统一多流程应用的路由和资源预算,修正标准详情子表展示,并让自动抄送在显式人数预算内支持最多200人。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"自动抄送可显式声明最多200人,未声明时仍默认20人;节点配置编辑器遵守原binding预算。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"浏览器路由校验与共享声明对齐2048路由、512资源,避免合法多流程应用被旧局部限制拒绝。",
|
|
12
|
+
"标准流程详情的PC子表与手机明细隐藏内部父关联、排序、hidden和system字段,保留业务值与顺序。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"开发多流程V2应用、维护自动抄送节点或使用标准流程详情的开发者与管理员。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"使用本批精确SDK组合,并同步支持新自动抄送预算的Server/Notification Hub;共享编译器摘要须一致。本候选先本地验证,未自动发布npm或学校生产。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"旧绑定与已运行实例不自动扩大人数;人工抄送仍最多20人,角色源最多200有效成员行,不能截断。",
|
|
22
|
+
"单实例历史仍受1000审批/自动抄送席位与2MiB读取预算约束。学校实际50人投递与性能尚未验。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "共享编译器同源配对;超过20人的自动抄送需同步升级Workflow与Notification Hub",
|
|
28
|
+
"v1": "V1不消费本批V2契约"
|
|
29
|
+
},
|
|
30
|
+
"sha256": "fa3fb90b3634bafbb7aedb48b26dd3ac5779a2375873cb90f1e9a16222944647",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.7"
|
|
32
|
+
}
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.6.0",
|
|
4
|
+
"title": "统一应用时区与日期时间输入",
|
|
5
|
+
"status": "reviewed",
|
|
6
|
+
"summary": "应用可指定业务展示时区,标准字段、审批详情、待办、通知和审计时间统一显示,日期时间输入仍保存 UTC。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"OpenXiangdaApplication 和 OpenXiangdaUiProvider 接受可选 timeZone;日期时间字段可覆盖时区并声明 min、max 和 minuteStep。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"修复设备时区不同导致日期时间编辑和公共详情、中心时间不一致的问题,拒绝夏令时不存在或重复的本地时间。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"需要固定业务时区或限制日期时间输入的 V2 应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"compatibility": {
|
|
17
|
+
"node": ">=24",
|
|
18
|
+
"workspaceGenerations": [
|
|
19
|
+
"v1",
|
|
20
|
+
"v2"
|
|
21
|
+
],
|
|
22
|
+
"v1Policy": "V1 引擎和已有应用不变。",
|
|
23
|
+
"platformPolicy": "展示与输入能力,无新增服务端契约或数据库迁移。未配置时区和限制的应用保留设备本地行为。"
|
|
24
|
+
},
|
|
25
|
+
"upgradeSteps": [
|
|
26
|
+
"将应用精确依赖升级至 openxiangda 2.6.0,更新锁文件并刷新技能资料。",
|
|
27
|
+
"在应用入口指定业务 timeZone,验证 PC 和移动端编辑、审批摘要与各中心显示。"
|
|
28
|
+
],
|
|
29
|
+
"knownLimitations": [
|
|
30
|
+
"时区只影响呈现;服务端仍须独立验证业务时间窗口和授权。",
|
|
31
|
+
"手机指定时区的日期时间滚轮提供当前选择前后各 365 天并按限制收窄;夏令时重复时间需选择其他无歧义时间。",
|
|
32
|
+
"包发布、应用部署和实际业务验收分别验证。"
|
|
33
|
+
],
|
|
34
|
+
"issues": [],
|
|
35
|
+
"sha256": "ba11ac3a69cbd9dd27e339c1d84642af99e107ca1170f0876b8be0583abda79f",
|
|
36
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.6.0"
|
|
37
|
+
}
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.7.0",
|
|
4
|
+
"title": "应用统一保护未保存内容",
|
|
5
|
+
"status": "reviewed",
|
|
6
|
+
"summary": "自定义表单可注册未保存状态,应用统一处理站内跳转、浏览器历史和刷新关闭提示。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"增加 useUnsavedChangesGuard,聚合多个表单的未保存状态,取消导航保留输入和原位置,提交成功后解除保护。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"补齐原 BrowserRouter 无法使用标准 useBlocker 导致自定义表单浏览器前进后退未受保护的问题。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"有自定义录入页面、异步提交或未知结果恢复的 V2 应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"compatibility": {
|
|
17
|
+
"node": ">=24",
|
|
18
|
+
"workspaceGenerations": [
|
|
19
|
+
"v1",
|
|
20
|
+
"v2"
|
|
21
|
+
],
|
|
22
|
+
"v1Policy": "V1 引擎和已有应用不变。",
|
|
23
|
+
"platformPolicy": "公共 React 路由生命周期调整,无服务端契约或数据库变更;应用仍使用既有 Routes、Link 和 navigate。"
|
|
24
|
+
},
|
|
25
|
+
"upgradeSteps": [
|
|
26
|
+
"精确升级到 openxiangda 2.7.0 并刷新技能资料。",
|
|
27
|
+
"在应用入口内使用 useUnsavedChangesGuard,涵盖未保存内容和结果未知状态,验证成功后解除以及取消后的输入保留。"
|
|
28
|
+
],
|
|
29
|
+
"knownLimitations": [
|
|
30
|
+
"原生刷新/关闭提示受浏览器限制,不能自定义提示文字。",
|
|
31
|
+
"该能力不持久化草稿或代替原提交回执恢复;应用不得直接操作 history.pushState。",
|
|
32
|
+
"包发布、应用部署与真实业务验收分别验证。"
|
|
33
|
+
],
|
|
34
|
+
"issues": [],
|
|
35
|
+
"sha256": "e8af0fc7c484cad1dc59ce982432e6a2fd4451d7f455141edc2d6128a057542e",
|
|
36
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.7.0"
|
|
37
|
+
}
|