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,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.32.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.32.0:自定义后台壳层与精确时间交互",
|
|
6
|
+
"summary": "提供正式后台壳层扩展,改进时间禁选、业务错误与内网开发诊断。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"应用可通过 ui.admin 提供完整后台壳层或顶栏、侧栏、页脚插槽,消费权限过滤后的导航与身份。",
|
|
9
|
+
"消息与待办导航可分别配置显示,资源深链接与移动端页面统一使用自定义壳层。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"日期时间控件按时区精确禁用小时、分钟、秒,保留输入校验和受控值。",
|
|
13
|
+
"业务拒绝的中文 message 与错误码、requestId 分离,避免页面丢失实际提示。",
|
|
14
|
+
"开发连接故障区分 DNS、TCP、TLS 与超时并提供安全恢复提示。"
|
|
15
|
+
],
|
|
16
|
+
"affectedUsers": [
|
|
17
|
+
"使用自定义管理后台、精确日期范围或校内网络开发的 V2 应用。"
|
|
18
|
+
],
|
|
19
|
+
"upgradeSteps": [
|
|
20
|
+
"升级 openxiangda 至 2.32.0,重新安装依赖并构建应用。CLI 模板随同版本化。",
|
|
21
|
+
"按公开 ui.admin 契约接入壳层;路由、登录与授权继续由平台负责。",
|
|
22
|
+
"基础记录字段默认读取及受管下载文件名需要配套平台后端升级;仅升级 npm 不会更改服务端。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"自定义壳层接入和业务页面设计仍由应用负责,升级 SDK 不自动替换现有 UI。",
|
|
26
|
+
"网络诊断不自动改变 VPN、系统代理、证书或重试未知结果写请求。",
|
|
27
|
+
"前端时间禁选不能替代应用服务端业务时间守卫。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"workspaceGenerations": "v2",
|
|
33
|
+
"platform": "沿用现有认证、权限与路由协议;基础记录元数据的后端调整需对应站点发布。",
|
|
34
|
+
"v1": "V1 引擎与既有业务不受本次 SDK 改动影响。"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "987351f0bde76980d80f2a1ea8741c7e4697ef7b659ca679f5bf9b2797c8e8b2",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.32.0"
|
|
38
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.33.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.33.0:事务构建与部署前置诊断",
|
|
6
|
+
"summary": "在提交前定位事务组合错误,在构建前发现平台依赖故障。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"openxiangda/nest 提供 createDataTransaction、diagnoseDataTransaction 和结构化构建错误。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"支持平台实时前置检查,发现内核、源码托管及镜像仓故障时停止后续构建。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"编写后端事务或向私有平台部署应用的 V2 开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"升级 openxiangda 到 2.33.0 并重新安装依赖。",
|
|
18
|
+
"平台部署对应后端后自动启用前置诊断;事务构建器按文档显式接入。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"只读预检不保证后续写入或容量;原有部署和权限检查继续执行。",
|
|
22
|
+
"事务构建不自动合并重复写入,不替代服务端权限和并发判断。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "前置检查按平台 capability 启用,旧站保持原部署流程。",
|
|
29
|
+
"v1": "V1 引擎与业务不变。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "6738fcde83daed062691a30f4c4161d5f59b8024303ba2c4c7fd377c6886de70",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.33.0"
|
|
33
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.0:持久排队业务计划与结果恢复",
|
|
6
|
+
"summary": "新增由平台持久受理并自动处理的业务命令,支持关闭页面后继续执行与本人跨设备恢复。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"新增 durable 受管命令、独立能力门禁、有界参数及生成的 backend-plan handler 清单。",
|
|
9
|
+
"openxiangda/nest 提供受执行证明约束的只读计划 handler,平台负责最终原子提交。",
|
|
10
|
+
"openxiangda/react 与 mobile 提供 useDurableCommand,支持显式提交、原键恢复、本人结果和退避轮询。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"严格区分内置 permit 配额所有权与应用 durable 计划,普通业务模型无需迁移到命令独占所有权。",
|
|
14
|
+
"执行上下文拒绝普通 SDK 写入、事务、通知和 OAuth,读取响应验证标准记录结构。"
|
|
15
|
+
],
|
|
16
|
+
"affectedUsers": [
|
|
17
|
+
"构建活动报名、预约、抢票及其他需要持久排队事务的 V2 应用开发者。"
|
|
18
|
+
],
|
|
19
|
+
"upgradeSteps": [
|
|
20
|
+
"升级 openxiangda 到 2.34.0,重新安装依赖并生成应用契约。",
|
|
21
|
+
"先部署支持 data.managed-concurrency.durable@1.0.0 的平台,再声明 durable 命令、handler manifest 和前端恢复流程。",
|
|
22
|
+
"在隔离测试数据上验证关闭浏览器、原请求恢复、取消后重报和业务原子结果,再分级测量实际容量。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"应用只返回受声明约束的事务计划,不能在 handler 内发送通知或调用普通写入接口。",
|
|
26
|
+
"受理成功不等于业务成功;队列位置为近似投影,不能推导精确等待时间或服务器容量。",
|
|
27
|
+
"旧 permit 模式保留,未升级平台会拒绝 durable 包;回滚前须停止新受理并核对已有请求。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"workspaceGenerations": "v2",
|
|
33
|
+
"platform": "durable 必须具备 data.managed-concurrency.durable@1.0.0,旧 permit 契约继续支持。",
|
|
34
|
+
"v1": "V1 引擎与业务不变。"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "929abb0ea8cdbb32e38c39131540cd64a248c4e1a68dbde9ff187f35438f8da0",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.0"
|
|
38
|
+
}
|
|
@@ -0,0 +1,34 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.1:持久申请受理恢复预算",
|
|
6
|
+
"summary": "支持配置最长30分钟的自动受理恢复,并保留首次明确提交时间和原申请编号。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"useDurableCommand 可用 acceptanceRecoveryMs 配置120秒至30分钟的受理恢复预算。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"刷新及恢复原申请不再重新计算受理重试预算;截止后保留查询和迟到结果恢复能力。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"需要较长排队等待的活动报名、预约和抢票应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"升级 openxiangda 到2.34.1,在需要长时间恢复的业务明确配置 acceptanceRecoveryMs。",
|
|
18
|
+
"验证原键恢复、截止后查询、未知应答及目标环境的完整排队容量。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"默认受理恢复预算仍为120秒;配置值是客户端自动入队预算,不是服务端最终完成承诺。",
|
|
22
|
+
"旧意图没有首次时间时,只能从首次明确恢复计时,无法证明历史发起时间。",
|
|
23
|
+
"受理成功不等于报名成功;实际容量需使用独立用户在目标环境验证。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"workspaceGenerations": "v2",
|
|
29
|
+
"platform": "沿用 data.managed-concurrency.durable@1.0.0;不改变平台事实和permit协议。",
|
|
30
|
+
"v1": "V1引擎及业务不变。"
|
|
31
|
+
},
|
|
32
|
+
"sha256": "f7297f5c779f079b48aa95ef594c9b4d7c373207467e1410aacfda57ca361451",
|
|
33
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.1"
|
|
34
|
+
}
|
|
@@ -0,0 +1,36 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.2:受管读取繁忙恢复与原申请观察期限",
|
|
6
|
+
"summary": "为受管只读查询提供有界退避,并使持久申请观察遵守原始三十分钟期限,真实依赖和权限故障立即显露。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"受管详情、本人申请、命令结果和配额查询默认最多恢复120秒、12次请求,可通过budgetMs或AbortSignal收窄。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"读取恢复冻结原参数及身份,遵循服务端Retry-After,只重试明确的容量繁忙;写请求保持单次发送。",
|
|
12
|
+
"已受理申请以原首次提交时间观察,跨设备使用原acceptedAt;刷新不会延长期限,超期后保留原编号用于显式查询。",
|
|
13
|
+
"持久结果轮询不再吞掉真实网络、依赖和权限故障。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"使用受管读取和持久排队能力的活动报名、预约及抢票应用开发者。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"将应用openxiangda精确依赖升级到2.34.2,刷新同版本资料后检查并部署测试环境。",
|
|
20
|
+
"验证繁忙恢复、故障提示、原键跨设备恢复及三十分钟期限;在目标硬件测量完整混合负载。"
|
|
21
|
+
],
|
|
22
|
+
"knownLimitations": [
|
|
23
|
+
"读取恢复仅覆盖明确只读方法;普通Data API和写入没有新增自动重试。",
|
|
24
|
+
"默认受理恢复预算仍为120秒,accepted观察最长三十分钟;客户端预算不承诺服务端完成时间。",
|
|
25
|
+
"自动观察停止后可能存在迟到结果,应查询原申请;容量仍需目标环境实测。"
|
|
26
|
+
],
|
|
27
|
+
"issues": [],
|
|
28
|
+
"compatibility": {
|
|
29
|
+
"node": ">=24",
|
|
30
|
+
"workspaceGenerations": "v2",
|
|
31
|
+
"platform": "沿用data.managed-concurrency.durable@1.0.0,兼容已知API_BUSY/RESULT_BUSY的旧503;新入口预算429需匹配平台版本。",
|
|
32
|
+
"v1": "V1引擎及业务不变。"
|
|
33
|
+
},
|
|
34
|
+
"sha256": "93594d8cc407bef730868e32737ba3e78ca5df955e2d33bc0bb3f6eec8f1d1f9",
|
|
35
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.2"
|
|
36
|
+
}
|
|
@@ -0,0 +1,35 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.34.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.34.3:显式长期只读繁忙恢复",
|
|
6
|
+
"summary": "允许热点详情等只读页面显式选择最长三十分钟恢复;默认两分钟策略及持久申请原期限保持,取消与真实故障仍及时结束。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"受管read、mine、result、allocation可显式设置budgetMs,超过120秒时最多恢复30分钟、120次请求;默认120秒和12次保持。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"长期读取仍冻结原输入、身份与权限视角,按原调用截止及Retry-After/抖动退避;AbortSignal中止请求和等待。",
|
|
12
|
+
"持久申请控制器显式保留原单次120秒上限,防止SDK扩展隐式改变既有受理和观察行为。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"使用受管热点详情和持久排队能力的活动报名、预约及抢票应用开发者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"将应用openxiangda精确升级到2.34.3并刷新资料;应用按业务选择显式预算、离页取消及未结束窗口的固定截止。",
|
|
19
|
+
"验证繁忙恢复、真实网络/权限/依赖错误、身份切换和持久申请原期限后部署测试环境,目标硬件容量另外实测。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"仅已知只读繁忙恢复;不吞未知429、网络、权限或依赖失败,不自动重试写入。",
|
|
23
|
+
"客户端等待窗口不承诺服务端容量或最终处理时间,不代表已经受理或报名。",
|
|
24
|
+
"长期恢复不自动启用,普通Data API、平台后端与V1业务不变;刷新固定窗口由应用生命周期接入。"
|
|
25
|
+
],
|
|
26
|
+
"issues": [],
|
|
27
|
+
"compatibility": {
|
|
28
|
+
"node": ">=24",
|
|
29
|
+
"workspaceGenerations": "v2",
|
|
30
|
+
"platform": "沿用data.managed-concurrency.durable@1.0.0;新入口429预算错误需要匹配平台版本。",
|
|
31
|
+
"v1": "V1引擎及业务不变。"
|
|
32
|
+
},
|
|
33
|
+
"sha256": "fe3ba4a4c33af0e158cbe5bb7b25c9ba4c75e4ef97a02479eded9c71885d00ec",
|
|
34
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.34.3"
|
|
35
|
+
}
|
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.35.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.35.0:运行时繁忙恢复与可读流程图",
|
|
6
|
+
"summary": "应用进入时可有界等待平台明确的繁忙响应,同身份刷新保留页面和原申请;流程图使用与不可变执行定义同源的投影展示说明、变量来源与实例路径。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"现有运行时 current 读取在明确的入口繁忙时按服务端提示和抖动退避,最长等待五分钟、最多一百二十次读取,并支持离页取消。",
|
|
9
|
+
"公开 WorkflowReadability、validateWorkflowReadability、projectWorkflowGraph 及共享 WorkflowDiagram,展示流程说明、条件优先级、变量来源和持久执行决定对应的路径,支持搜索、键盘及窄屏节点列表。",
|
|
10
|
+
"流程图使用懒加载 React Flow 与 ELK 正交布局,支持直角连线、平移缩放、节点定位、分支条件标签和缩略导航。",
|
|
11
|
+
"审批节点可显式声明管理员可调整的模式、人员来源和按钮上限;编译器复用有界校验,SDK 提供配置读取、CAS 更新和幂等回执,任务冻结有效配置。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [
|
|
14
|
+
"启动、焦点和可见性检查合并挂起身份读取;同身份刷新保留已验证页面和草稿,临时服务故障可重新检查,真实身份、环境、权限作用域变化或拒绝使旧受管客户端失效。",
|
|
15
|
+
"退出通知优先于仍在加载的身份请求,旧响应和取消回调不会恢复旧身份或覆盖登录入口。验证 current 成功后仅清除当前路径的入口等待截止。",
|
|
16
|
+
"安全只读传输故障最多三次总尝试;权限投影等待保留原十秒限制,普通应用请求和写入不会因本次修改自动重放。"
|
|
17
|
+
],
|
|
18
|
+
"affectedUsers": [
|
|
19
|
+
"使用 V2 运行时及持久排队能力的活动报名、预约、抢票应用开发者。",
|
|
20
|
+
"需要展示不可变流程定义、说明及实例执行路径,或启用有界审批节点配置的平台维护者和应用开发者。"
|
|
21
|
+
],
|
|
22
|
+
"upgradeSteps": [
|
|
23
|
+
"将应用 openxiangda 精确升级到 2.35.0;平台流程图消费者将 openxiangda-contracts 精确升级到 2.35.0,同批工具链使用 openxiangda-devkit-core 2.36.0,更新锁文件。",
|
|
24
|
+
"统一验证运行时繁忙恢复、同身份刷新、退出与真实身份切换,以及流程图说明与持久执行路径后发布同一冻结候选;启用管理员节点配置时确认平台支持 workflow.node-administration。",
|
|
25
|
+
"在目标服务器另外测量完整页面进入、提交、自然结果查询及最终处理时间;客户端恢复测试不作为硬件并发容量证据。"
|
|
26
|
+
],
|
|
27
|
+
"knownLimitations": [
|
|
28
|
+
"运行时繁忙恢复只用于现有 current 读取;未知 429、权限或版本拒绝和非繁忙依赖失败不扩展等待,初始化成功不表示业务请求已经受理。",
|
|
29
|
+
"本次发布保留持久申请的原请求键、观察截止和自然轮询策略;队列的受理、执行和最终结果仍由平台负责。",
|
|
30
|
+
"流程图说明不改变不可变执行定义及持久实例决定,不补造不存在的执行边,也不改变流程授权。",
|
|
31
|
+
"管理员节点配置只调整应用明确开放的边界,字段行为继续由应用页面与代码维护;未声明该能力的应用不启用新的配置入口。"
|
|
32
|
+
],
|
|
33
|
+
"issues": [],
|
|
34
|
+
"compatibility": {
|
|
35
|
+
"node": ">=24",
|
|
36
|
+
"workspaceGenerations": "v2",
|
|
37
|
+
"platform": "入口繁忙恢复需要平台提供 CONCURRENCY_BOOTSTRAP_BUSY 或 CONCURRENCY_API_BUSY 契约;可读流程图需要匹配的只读平台接口,管理员节点配置需要 workflow.node-administration 能力。持久排队沿用 data.managed-concurrency.durable@1.0.0。",
|
|
38
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
39
|
+
},
|
|
40
|
+
"sha256": "4151d5e02c0b8a93c0bbf12bb23bf3cf5cd71387976b1e07f8033e2113603a3a",
|
|
41
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.35.0"
|
|
42
|
+
}
|
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.35.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.35.1:运行时繁忙恢复与可读流程图",
|
|
6
|
+
"summary": "应用进入时可有界等待平台明确的繁忙响应,同身份刷新保留页面和原申请;流程图使用与不可变执行定义同源的投影展示说明、变量来源与实例路径。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"现有运行时 current 读取在明确的入口繁忙时按服务端提示和抖动退避,最长等待五分钟、最多一百二十次读取,并支持离页取消。",
|
|
9
|
+
"公开 WorkflowReadability、validateWorkflowReadability、projectWorkflowGraph 及共享 WorkflowDiagram,展示流程说明、条件优先级、变量来源和持久执行决定对应的路径,支持搜索、键盘及窄屏节点列表。",
|
|
10
|
+
"流程图使用懒加载 React Flow 与 ELK 正交布局,支持直角连线、平移缩放、节点定位、分支条件标签和缩略导航。",
|
|
11
|
+
"审批节点可显式声明管理员可调整的模式、人员来源和按钮上限;编译器复用有界校验,SDK 提供配置读取、CAS 更新和幂等回执,任务冻结有效配置。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [
|
|
14
|
+
"启动、焦点和可见性检查合并挂起身份读取;同身份刷新保留已验证页面和草稿,临时服务故障可重新检查,真实身份、环境、权限作用域变化或拒绝使旧受管客户端失效。",
|
|
15
|
+
"退出通知优先于仍在加载的身份请求,旧响应和取消回调不会恢复旧身份或覆盖登录入口。验证 current 成功后仅清除当前路径的入口等待截止。",
|
|
16
|
+
"安全只读传输故障最多三次总尝试;权限投影等待保留原十秒限制,普通应用请求和写入不会因本次修改自动重放。",
|
|
17
|
+
"管理员流程节点配置使用平台已有的 admin controller,修正上下文、配置读取和保存地址,保留环境、CAS、幂等操作标识与权限拒绝。"
|
|
18
|
+
],
|
|
19
|
+
"affectedUsers": [
|
|
20
|
+
"使用 V2 运行时及持久排队能力的活动报名、预约、抢票应用开发者。",
|
|
21
|
+
"需要展示不可变流程定义、说明及实例执行路径,或启用有界审批节点配置的平台维护者和应用开发者。"
|
|
22
|
+
],
|
|
23
|
+
"upgradeSteps": [
|
|
24
|
+
"将应用 openxiangda 精确升级到 2.35.1;平台流程图消费者将 openxiangda-contracts 精确升级到 2.35.0,同批工具链使用 openxiangda-devkit-core 2.36.0 和 openxiangda-cli 2.6.19,更新锁文件。",
|
|
25
|
+
"统一验证运行时繁忙恢复、同身份刷新、退出与真实身份切换,以及流程图说明与持久执行路径后发布同一冻结候选;启用管理员节点配置时确认平台支持 workflow.node-administration。",
|
|
26
|
+
"在目标服务器另外测量完整页面进入、提交、自然结果查询及最终处理时间;客户端恢复测试不作为硬件并发容量证据。"
|
|
27
|
+
],
|
|
28
|
+
"knownLimitations": [
|
|
29
|
+
"运行时繁忙恢复只用于现有 current 读取;未知 429、权限或版本拒绝和非繁忙依赖失败不扩展等待,初始化成功不表示业务请求已经受理。",
|
|
30
|
+
"本次发布保留持久申请的原请求键、观察截止和自然轮询策略;队列的受理、执行和最终结果仍由平台负责。",
|
|
31
|
+
"流程图说明不改变不可变执行定义及持久实例决定,不补造不存在的执行边,也不改变流程授权。",
|
|
32
|
+
"管理员节点配置只调整应用明确开放的边界,字段行为继续由应用页面与代码维护;未声明该能力的应用不启用新的配置入口。"
|
|
33
|
+
],
|
|
34
|
+
"issues": [],
|
|
35
|
+
"compatibility": {
|
|
36
|
+
"node": ">=24",
|
|
37
|
+
"workspaceGenerations": "v2",
|
|
38
|
+
"platform": "入口繁忙恢复需要平台提供 CONCURRENCY_BOOTSTRAP_BUSY 或 CONCURRENCY_API_BUSY 契约;可读流程图需要匹配的只读平台接口,管理员节点配置需要 workflow.node-administration 能力。持久排队沿用 data.managed-concurrency.durable@1.0.0。",
|
|
39
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
40
|
+
},
|
|
41
|
+
"sha256": "80a635d3f30fc35010e13483dba6bf01245d2db6db80f6ee4ddc5e4f9b00efe0",
|
|
42
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.35.1"
|
|
43
|
+
}
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.35.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.35.2:运行时繁忙恢复与可读流程图",
|
|
6
|
+
"summary": "应用进入时可有界等待平台明确的繁忙响应,同身份刷新保留页面和原申请;流程图使用与不可变执行定义同源的投影展示说明、变量来源与实例路径。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"现有运行时 current 读取在明确的入口繁忙时按服务端提示和抖动退避,最长等待五分钟、最多一百二十次读取,并支持离页取消。",
|
|
9
|
+
"公开 WorkflowReadability、validateWorkflowReadability、projectWorkflowGraph 及共享 WorkflowDiagram,展示流程说明、条件优先级、变量来源和持久执行决定对应的路径,支持搜索、键盘及窄屏节点列表。",
|
|
10
|
+
"流程图使用懒加载 React Flow 与 ELK 正交布局,支持直角连线、平移缩放、节点定位、分支条件标签和缩略导航。",
|
|
11
|
+
"审批节点可显式声明管理员可调整的模式、人员来源和按钮上限;编译器复用有界校验,SDK 提供配置读取、CAS 更新和幂等回执,任务冻结有效配置。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [
|
|
14
|
+
"启动、焦点和可见性检查合并挂起身份读取;同身份刷新保留已验证页面和草稿,临时服务故障可重新检查,真实身份、环境、权限作用域变化或拒绝使旧受管客户端失效。",
|
|
15
|
+
"退出通知优先于仍在加载的身份请求,旧响应和取消回调不会恢复旧身份或覆盖登录入口。验证 current 成功后仅清除当前路径的入口等待截止。",
|
|
16
|
+
"安全只读传输故障最多三次总尝试;权限投影等待保留原十秒限制,普通应用请求和写入不会因本次修改自动重放。",
|
|
17
|
+
"管理员流程节点配置使用平台已有的 admin controller,修正上下文、配置读取和保存地址,保留环境、CAS、幂等操作标识与权限拒绝。",
|
|
18
|
+
"管理员流程节点配置保留平台返回的具体冲突错误码,页面可准确提示配置修订和幂等冲突。",
|
|
19
|
+
"StrictMode 同一提交的清理、重挂载接管原 current owner,避免重复初始化读取;观察取消立即生效,无人接管时释放共享请求,安装身份必须仍有活跃观察者,原读取预算与退出优先级保留。"
|
|
20
|
+
],
|
|
21
|
+
"affectedUsers": [
|
|
22
|
+
"使用 V2 运行时及持久排队能力的活动报名、预约、抢票应用开发者。",
|
|
23
|
+
"需要展示不可变流程定义、说明及实例执行路径,或启用有界审批节点配置的平台维护者和应用开发者。"
|
|
24
|
+
],
|
|
25
|
+
"upgradeSteps": [
|
|
26
|
+
"将应用 openxiangda 精确升级到 2.35.2;平台流程图消费者将 openxiangda-contracts 精确升级到 2.35.0,同批工具链使用 openxiangda-devkit-core 2.36.0 和 openxiangda-cli 2.6.20,更新锁文件。",
|
|
27
|
+
"统一验证运行时繁忙恢复、同身份刷新、退出与真实身份切换,以及流程图说明与持久执行路径后发布同一冻结候选;启用管理员节点配置时确认平台支持 workflow.node-administration。",
|
|
28
|
+
"在目标服务器另外测量完整页面进入、提交、自然结果查询及最终处理时间;客户端恢复测试不作为硬件并发容量证据。"
|
|
29
|
+
],
|
|
30
|
+
"knownLimitations": [
|
|
31
|
+
"运行时繁忙恢复只用于现有 current 读取;未知 429、权限或版本拒绝和非繁忙依赖失败不扩展等待,初始化成功不表示业务请求已经受理。",
|
|
32
|
+
"本次发布保留持久申请的原请求键、观察截止和自然轮询策略;队列的受理、执行和最终结果仍由平台负责。",
|
|
33
|
+
"流程图说明不改变不可变执行定义及持久实例决定,不补造不存在的执行边,也不改变流程授权。",
|
|
34
|
+
"管理员节点配置只调整应用明确开放的边界,字段行为继续由应用页面与代码维护;未声明该能力的应用不启用新的配置入口。"
|
|
35
|
+
],
|
|
36
|
+
"issues": [],
|
|
37
|
+
"compatibility": {
|
|
38
|
+
"node": ">=24",
|
|
39
|
+
"workspaceGenerations": "v2",
|
|
40
|
+
"platform": "入口繁忙恢复需要平台提供 CONCURRENCY_BOOTSTRAP_BUSY 或 CONCURRENCY_API_BUSY 契约;可读流程图需要匹配的只读平台接口,管理员节点配置需要 workflow.node-administration 能力。持久排队沿用 data.managed-concurrency.durable@1.0.0。",
|
|
41
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
42
|
+
},
|
|
43
|
+
"sha256": "40f817d86f1533912f177d5b129f9eb4d224a08af0d150366dc53111fc323615",
|
|
44
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.35.2"
|
|
45
|
+
}
|
|
@@ -0,0 +1,46 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.35.3",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.35.3:运行时繁忙恢复与可读流程图",
|
|
6
|
+
"summary": "应用进入时可有界等待平台明确的繁忙响应,同身份刷新保留页面和原申请;流程图使用与不可变执行定义同源的投影展示说明、变量来源与实例路径。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"现有运行时 current 读取在明确的入口繁忙时按服务端提示和抖动退避,最长等待五分钟、最多一百二十次读取,并支持离页取消。",
|
|
9
|
+
"公开 WorkflowReadability、validateWorkflowReadability、projectWorkflowGraph 及共享 WorkflowDiagram,展示流程说明、条件优先级、变量来源和持久执行决定对应的路径,支持搜索、键盘及窄屏节点列表。",
|
|
10
|
+
"流程图使用懒加载 React Flow 与 ELK 正交布局,支持直角连线、平移缩放、节点定位、分支条件标签和缩略导航。",
|
|
11
|
+
"审批节点可显式声明管理员可调整的模式、人员来源和按钮上限;编译器复用有界校验,SDK 提供配置读取、CAS 更新和幂等回执,任务冻结有效配置。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [
|
|
14
|
+
"启动、焦点和可见性检查合并挂起身份读取;同身份刷新保留已验证页面和草稿,临时服务故障可重新检查,真实身份、环境、权限作用域变化或拒绝使旧受管客户端失效。",
|
|
15
|
+
"退出通知优先于仍在加载的身份请求,旧响应和取消回调不会恢复旧身份或覆盖登录入口。验证 current 成功后仅清除当前路径的入口等待截止。",
|
|
16
|
+
"安全只读传输故障最多三次总尝试;权限投影等待保留原十秒限制,普通应用请求和写入不会因本次修改自动重放。",
|
|
17
|
+
"管理员流程节点配置使用平台已有的 admin controller,修正上下文、配置读取和保存地址,保留环境、CAS、幂等操作标识与权限拒绝。",
|
|
18
|
+
"管理员流程节点配置保留平台返回的具体冲突错误码,页面可准确提示配置修订和幂等冲突。",
|
|
19
|
+
"StrictMode 同一提交的清理、重挂载接管原 current owner,避免重复初始化读取;观察取消立即生效,无人接管时释放共享请求,安装身份必须仍有活跃观察者,原读取预算与退出优先级保留。",
|
|
20
|
+
"标准任务和实例详情按应用声明返回对应设备的用户流程中心,避免普通申请人被带入管理后台;独立详情组件可显式指定返回路径,抽屉关闭和页面授权保持原行为。"
|
|
21
|
+
],
|
|
22
|
+
"affectedUsers": [
|
|
23
|
+
"使用 V2 运行时及持久排队能力的活动报名、预约、抢票应用开发者。",
|
|
24
|
+
"需要展示不可变流程定义、说明及实例执行路径,或启用有界审批节点配置的平台维护者和应用开发者。"
|
|
25
|
+
],
|
|
26
|
+
"upgradeSteps": [
|
|
27
|
+
"将应用 openxiangda 精确升级到 2.35.3;平台流程图消费者将 openxiangda-contracts 精确升级到 2.35.0,同批工具链使用 openxiangda-devkit-core 2.36.0 和 openxiangda-cli 2.6.21,更新锁文件。",
|
|
28
|
+
"统一验证运行时繁忙恢复、同身份刷新、退出与真实身份切换,以及流程图说明与持久执行路径后发布同一冻结候选;启用管理员节点配置时确认平台支持 workflow.node-administration。",
|
|
29
|
+
"在目标服务器另外测量完整页面进入、提交、自然结果查询及最终处理时间;客户端恢复测试不作为硬件并发容量证据。"
|
|
30
|
+
],
|
|
31
|
+
"knownLimitations": [
|
|
32
|
+
"运行时繁忙恢复只用于现有 current 读取;未知 429、权限或版本拒绝和非繁忙依赖失败不扩展等待,初始化成功不表示业务请求已经受理。",
|
|
33
|
+
"本次发布保留持久申请的原请求键、观察截止和自然轮询策略;队列的受理、执行和最终结果仍由平台负责。",
|
|
34
|
+
"流程图说明不改变不可变执行定义及持久实例决定,不补造不存在的执行边,也不改变流程授权。",
|
|
35
|
+
"管理员节点配置只调整应用明确开放的边界,字段行为继续由应用页面与代码维护;未声明该能力的应用不启用新的配置入口。"
|
|
36
|
+
],
|
|
37
|
+
"issues": [],
|
|
38
|
+
"compatibility": {
|
|
39
|
+
"node": ">=24",
|
|
40
|
+
"workspaceGenerations": "v2",
|
|
41
|
+
"platform": "入口繁忙恢复需要平台提供 CONCURRENCY_BOOTSTRAP_BUSY 或 CONCURRENCY_API_BUSY 契约;可读流程图需要匹配的只读平台接口,管理员节点配置需要 workflow.node-administration 能力。持久排队沿用 data.managed-concurrency.durable@1.0.0。",
|
|
42
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
43
|
+
},
|
|
44
|
+
"sha256": "31ce7268d3e443bf8fd5d26f0be82be6b1a24ff22f25d0735c7abf4a83fe92dd",
|
|
45
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.35.3"
|
|
46
|
+
}
|
|
@@ -0,0 +1,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.36.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.36.0:代码限定的审批人路由维护",
|
|
6
|
+
"summary": "审批绑定可声明路由策略,管理员按代码开放的维度和人员来源维护通用及专项规则;标准页与应用 SDK 复用同一维护组件。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"审批绑定支持最多 8 个事实维度和 16 个应用角色或范围角色来源,规则支持通用/专项追加、唯一最高优先级替换及时间窗。",
|
|
9
|
+
"公开路由配置、目录、分页历史及带 Head/规则修订和 operationId 的 CAS 保存合同。",
|
|
10
|
+
"公开 WorkflowAssignmentRoutingManager 与 WorkflowAssignmentRoutingEditor,支持规则草稿、差异核对、冲突后保留草稿、未知结果原请求恢复和关闭保护。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"审批人路由能力进入应用打包及目标预检的使用摘要,保持与共享 Native compiler 的严格能力闭包一致。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"需要由管理员维护审批人追加/替换规则的平台维护者和 V2 应用开发者。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"精确升级 openxiangda 2.36.0、contracts 2.36.0、devkit-core 2.37.0 和 CLI 2.6.22 的同批包并更新锁文件;本地测试可消费该批文件制品。",
|
|
20
|
+
"目标平台必须支持 workflow.assignment-routing@1.0.0;匹配平台随 V2 内核提供该能力,应用无需手填能力清单或额外开启开关。",
|
|
21
|
+
"在绑定代码中声明 routing,并在现有管理后台嵌入共享维护组件;按实际角色验证规则、CAS、旧任务冻结、拒绝及恢复后再交付业务。"
|
|
22
|
+
],
|
|
23
|
+
"knownLimitations": [
|
|
24
|
+
"首版来源只开放 app_role 和 app_role_in_scope;身份与成员仍由平台 AuthZ 维护,路由维护只允许应用超级管理员。",
|
|
25
|
+
"规则最多 256 条/256 KiB,最多 64 条匹配、200 个候选;最高优先级替换冲突明确阻塞。",
|
|
26
|
+
"保存影响未来节点进入,已有任务保持快照;字段行为、条件计算和拓扑仍由应用代码维护。",
|
|
27
|
+
"本批不代表完整账号资格、代理、学校业务等价或生产迁移完成。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"workspaceGenerations": "v2",
|
|
33
|
+
"platform": "workflow.assignment-routing@1.0.0;共享配置校验及平台路由接口须采用同批合同。",
|
|
34
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
35
|
+
},
|
|
36
|
+
"sha256": "71c1360ba0c0df98854f79ccd7d4b19be0dfe35da0f518fbb82d8fd54013f2f3",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.36.0"
|
|
38
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.36.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.36.1:审批人路由草稿核对与窄屏修复",
|
|
6
|
+
"summary": "路由草稿按内容核对,打开表单后原样加入不产生多余修改;窄屏搜索与刷新工具栏可以换行。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"路由规则草稿及变更核对忽略 JSON 对象键的插入顺序,保留所有字段值和数组顺序,避免表单往返被误算为修改。",
|
|
10
|
+
"审批人路由工具栏允许换行并约束搜索框宽度,防止窄屏后台产生外层横向溢出。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用 WorkflowAssignmentRoutingManager 或 WorkflowAssignmentRoutingEditor 维护审批规则的平台管理员及 V2 应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"精确升级 openxiangda 2.36.1 和 CLI 2.6.23 并更新锁文件;其余同批依赖保持 2.36.0 路由组合。",
|
|
17
|
+
"在标准页或 SDK 工具页打开已有规则后原样加入,确认没有多余核对项;在窄屏验证搜索、刷新和表格内部滚动。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"修订冲突后载入最新基准会保留完整草稿,不自动合并其他管理员的修改,保存前仍需逐项核对。",
|
|
21
|
+
"本次仅修复共享管理界面,不改变人员解析、权限、规则生效范围或当前待办快照;字段行为仍由页面代码维护。",
|
|
22
|
+
"本地实验室包验证与 npm 发布分开记录,本轮不代表完整 M2 或学校业务迁移完成。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "继续使用 workflow.assignment-routing@1.0.0 与 2.36.0 路由平台合同。",
|
|
29
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "011777999c79368eef6c5df4200d74455ca3eb3298bcad693967a5c6af526b73",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.36.1"
|
|
33
|
+
}
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.37.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.37.0:共享角色成员维护与逐项回执",
|
|
6
|
+
"summary": "标准管理入口与应用工具页共享成员维护组件,支持有界批量差异核对、原操作恢复及版本化潜在流程引用。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"RoleMembershipManager 提供角色、人员、状态及业务范围筛选,支持最多 50 项的新增、完整范围/有效期调整和撤销。",
|
|
9
|
+
"预览通过真实原生授权内核验证后回滚全部写入;执行按项独立事务,复用 CAS、权限、不可变回执与授权缓存所有者。",
|
|
10
|
+
"潜在流程引用按激活及在途固定版本列出代码默认、节点覆盖及代码许可路由来源,服务端限定版本、字节、节点和分页预算。",
|
|
11
|
+
"冲突后显式载入最新基准并保留输入;未知结果保留原编号及请求,以原回执核对或显式重试。"
|
|
12
|
+
],
|
|
13
|
+
"fixes": [
|
|
14
|
+
"既有管理 scope-values 读面使用独立 id/label/offset 合同,避免与数据字段选择器 value/label/cursor 的协议混用。"
|
|
15
|
+
],
|
|
16
|
+
"affectedUsers": [
|
|
17
|
+
"维护应用职责成员的平台管理员、受托角色管理员及嵌入通用管理工具的 V2 应用开发者。"
|
|
18
|
+
],
|
|
19
|
+
"upgradeSteps": [
|
|
20
|
+
"精确升级 openxiangda 2.37.0、contracts 2.37.0 与机器生成的同批 CLI/SDK 依赖并更新锁文件;本地实验室可消费同批 tgz。",
|
|
21
|
+
"平台需要 authz.native-membership-batch@1.0.0 和 workflow.role-references@1.0.0,随更新后的 V2 平台自动启用。",
|
|
22
|
+
"在既有授权后台页面嵌入 RoleMembershipManager,检查当前用户目录、预览差异、部分失败、CAS 和原回执恢复。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"成员管理委托按角色和动作,不新增按部门委派权限;仅成员维护权不授予关联流程管理读取权。",
|
|
26
|
+
"修改成员影响后续授权和分派,已有待办保留参与快照,办理仍实时复核资格;潜在引用数量不是受影响待办数。",
|
|
27
|
+
"批量执行允许部分成功;未知结果和回执 404 不能当作未提交,必须保留原请求。",
|
|
28
|
+
"字段行为继续由页面代码维护。本地包与实验室部署验收单独记录,此说明不代表 npm 发布、完整 M2 或学校迁移完成。"
|
|
29
|
+
],
|
|
30
|
+
"issues": [],
|
|
31
|
+
"compatibility": {
|
|
32
|
+
"node": ">=24",
|
|
33
|
+
"workspaceGenerations": "v2",
|
|
34
|
+
"platform": "NativeAuthZ 与 Workflow 原所有者,新增自动能力合同和只读引用;稳定生产管理端保留已发布组合。",
|
|
35
|
+
"v1": "V1 分发引擎及业务不变。"
|
|
36
|
+
},
|
|
37
|
+
"sha256": "ac4502b6860e55e973a8bfd7bb5741cc0a82da306087ffef8e1e1138f7fa04ca",
|
|
38
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.37.0"
|
|
39
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.37.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.37.1:成员维护窄屏和提交状态修复",
|
|
6
|
+
"summary": "修复实际成员维护验收发现的默认侧边栏折叠、读取失败提示与保存期间按钮状态。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"默认应用 Shell 补齐响应式断点,小屏自动折叠侧边栏,为共享成员维护组件保留内容宽度。",
|
|
10
|
+
"成员读取失败和加载状态各自显示对应提示,避免把尚未读到的数据解释为空成员。",
|
|
11
|
+
"预览、提交和原编号重试期间显式禁用操作按钮,与关闭和草稿锁保持一致。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用默认应用 Shell 或共享 RoleMembershipManager 的 V2 应用开发者和成员维护人员。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"使用机器生成的同批 openxiangda 2.37.1、CLI 与依赖组合,更新冻结锁文件;本地可消费同批 tgz。",
|
|
18
|
+
"在窄屏和桌面核验角色筛选、成员核对、保存锁与未知结果恢复。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"自定义 Shell 仍由宿主负责可收缩内容宽度。",
|
|
22
|
+
"本次本地包修复不代表 npm 发布、M2 整体验收或学校生产迁移;字段行为由页面代码维护。"
|
|
23
|
+
],
|
|
24
|
+
"issues": [],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"workspaceGenerations": "v2",
|
|
28
|
+
"platform": "沿用原成员、代理和流程管理授权合同。",
|
|
29
|
+
"v1": "沿用原 V1 分发。"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "be42c40f20a7311a0074bfba7f3202a76cd668ec350c73940d0d0958ff0994bb",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.37.1"
|
|
33
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.37.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.37.2:分配成员初始目录查询修复",
|
|
6
|
+
"summary": "共享成员维护组件在输入有效姓名或账号后查询分页目录,初次打开、清空或短词不再发出无效请求,已选人员标签保留。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"修复分配成员初始目录查询触发OPENXIANGDA_DIRECTORY_KEYWORD_INVALID的问题;搜索词至少2个字符或1个汉字、最多64个字符,保持分页、人员资格与当前用户授权。"
|
|
10
|
+
],
|
|
11
|
+
"affectedUsers": [
|
|
12
|
+
"使用RoleMembershipManager分配角色成员的管理员和V2应用开发者。"
|
|
13
|
+
],
|
|
14
|
+
"upgradeSteps": [
|
|
15
|
+
"升级机器生成的同批openxiangda 2.37.2和CLI组合,更新冻结锁文件。",
|
|
16
|
+
"核验初次打开成员选择、搜索人员和清空搜索;本地实验室可使用同批tgz。"
|
|
17
|
+
],
|
|
18
|
+
"knownLimitations": [
|
|
19
|
+
"目录搜索和成员维护仍受平台当前用户授权及有界分页约束。",
|
|
20
|
+
"本批本地修复不代表npm发布或学校生产迁移;字段行为由页面代码维护。"
|
|
21
|
+
],
|
|
22
|
+
"issues": [],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"workspaceGenerations": "v2",
|
|
26
|
+
"platform": "沿用原角色和目录协议。",
|
|
27
|
+
"v1": "沿用原V1分发。"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "cc915a0f12f322ef20bb1455e587a40558e2add3779f651155f990f0cbd2ad2c",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.37.2"
|
|
31
|
+
}
|