openxiangda 2.75.4 → 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 -25
- 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.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.63.0.json +0 -45
- package/releases/2.63.1.json +0 -46
- package/releases/2.66.0.json +0 -29
- package/releases/2.66.1.json +0 -29
- package/releases/2.66.2.json +0 -29
- package/releases/2.67.0.json +0 -33
- package/releases/2.67.1.json +0 -35
- package/releases/2.68.2.json +0 -33
- package/releases/2.70.0.json +0 -35
- package/releases/2.70.1.json +0 -34
- package/releases/2.75.2.json +0 -34
- package/releases/2.75.4.json +0 -31
|
@@ -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,37 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.58.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "有界入口读取恢复与流程、开发配置能力更新",
|
|
6
|
+
"summary": "身份读取在原期限内恢复短暂网络失败;同时交付主线已合入的流程范围、主子事务和开发配置能力。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"具名流程支持保存前范围候选与一层 owned 主子创建闭包,仍由平台按实际资料及职责校验。",
|
|
9
|
+
"流程节点支持有界职责成员并集及可选操作原因,任务使用进入节点时冻结的规则。",
|
|
10
|
+
"显式 owned 子表支持最多500行及有界记录集合事务守卫,保留 CAS、字节与文件限额。",
|
|
11
|
+
"预发布开发配置可同步真实 Native 配置而不构建 Web/Nest 制品,不能晋级生产。",
|
|
12
|
+
"连接开发支持从源码接收有界后端事件交付,保留真实平台租约和确认边界。"
|
|
13
|
+
],
|
|
14
|
+
"fixes": [
|
|
15
|
+
"身份 GET 不再因第三次短暂传输失败提前退出;采用有界指数退避,保留原恢复截止、单次超时、取消与明确权限拒绝。"
|
|
16
|
+
],
|
|
17
|
+
"affectedUsers": [
|
|
18
|
+
"使用 V2 入口等待、具名流程、owned 子表或预发布开发配置的应用。"
|
|
19
|
+
],
|
|
20
|
+
"upgradeSteps": [
|
|
21
|
+
"消费同源完整发行组合,并按声明协商目标平台能力。",
|
|
22
|
+
"入口预约、身份回执恢复和结果查询提示需配套平台更新;更新后重新校准真实页面请求图及性能测试。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"本轮尚未完成客户站点部署及新版本容量验收;源码验证不代表线上通过。",
|
|
26
|
+
"入口恢复仅重试读取,不自动重放报名等业务写操作,不续期原 Redis 票据。",
|
|
27
|
+
"此前8000人实验有7989人客户端30分钟内读回,最高完整通过仍5000人;实验不含SSO,不能代替首秒8000人完整浏览器容量结论。"
|
|
28
|
+
],
|
|
29
|
+
"issues": [],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"platform": "按声明协商对应 Native 与流程能力;入口恢复配套平台回执",
|
|
33
|
+
"v1": "V1不消费该V2接口"
|
|
34
|
+
},
|
|
35
|
+
"sha256": "ac8676f79afa9bc596508c7ca897ec60ffadf79f86ca36429dc1a279df23cf09",
|
|
36
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.58.0"
|
|
37
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.58.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "同源交付记录流程历史及入口读取恢复",
|
|
6
|
+
"summary": "根包和模板消费新增 Nest 记录流程历史接口,并保留2.58.0的入口读取恢复与能力更新。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"Nest 用户上下文支持业务记录流程历史读取,复用 Native/RLS、记录实例绑定、分页及修订校验。"
|
|
9
|
+
],
|
|
10
|
+
"fixes": [
|
|
11
|
+
"统一根包、CLI模板与Nest的精确发行版本,避免混用新增接口和旧归档。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用 Nest 工作流记录历史或入口等待恢复的V2应用。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"安装完整同源发行组合;入口预约与结果查询退避需要配套平台更新并重新校准请求图。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"2.58.0及本批尚未完成客户站点新候选容量验收;上一轮8000人仅7989人客户端30分钟内读回,最高完整通过仍5000人。",
|
|
21
|
+
"不改变流程办理权限,不自动重放业务写操作,不覆盖SSO集中登录容量。"
|
|
22
|
+
],
|
|
23
|
+
"issues": [],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "复用平台当前用户记录流程历史与V2入口能力",
|
|
27
|
+
"v1": "V1不消费该V2接口"
|
|
28
|
+
},
|
|
29
|
+
"sha256": "9e7fb09dc8b7a0de8fff5e955e7d35cb4d4d1ce1be5fa1105a5d2c2517de6414",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.58.1"
|
|
31
|
+
}
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.59.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "入口排队观察节奏与同源契约升级",
|
|
6
|
+
"summary": "尊重服务器入口排队查询间隔,并发行主线已评审的owned聚合容量及固定工作流阶段事务能力。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型可声明最高1000行的owned聚合容量,缺省500行、单子表500行与原子编辑边界不变。",
|
|
9
|
+
"固定且已协调的工作流阶段可显式启用一次阶段绑定的Native数据事务,并恢复原事务回执。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"入口身份读取不再把60秒服务端查询提示压缩为15秒,保留最低间隔、抖动、原截止、取消及权限拒绝边界。",
|
|
13
|
+
"CLI模板使用本次根SDK精确版本,保证新建应用与发行能力一致。"
|
|
14
|
+
],
|
|
15
|
+
"affectedUsers": [
|
|
16
|
+
"启用入口等待的V2应用,以及使用新增可选owned容量或工作流阶段事务声明的应用。"
|
|
17
|
+
],
|
|
18
|
+
"upgradeSteps": [
|
|
19
|
+
"精确安装完整同源发行组合;新增契约需匹配平台能力。高并发应用在真实页面和隔离HTTP请求图中校准查询节奏。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"本次客户万人复测尚未执行。上轮已登录万人HTTP图30分钟客户端与数据对账通过,严格网关对账仍保留18条已dispatch缺行。",
|
|
23
|
+
"不自动重放业务写入,不扩大权限或刷新原截止;不证明集中SSO、万人同秒提交、浏览器渲染容量或硬件绝对上限。"
|
|
24
|
+
],
|
|
25
|
+
"issues": [],
|
|
26
|
+
"compatibility": {
|
|
27
|
+
"node": ">=24",
|
|
28
|
+
"platform": "新增声明按目标平台能力协商;共享契约须消费同源版本",
|
|
29
|
+
"v1": "V1不消费本批V2运行时能力"
|
|
30
|
+
},
|
|
31
|
+
"sha256": "f6d7b5a8d416ba728f598cd0e24680fb13ffab779a5ad568d306e02c0e77f5bf",
|
|
32
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.59.2"
|
|
33
|
+
}
|
|
@@ -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,38 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.60.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.60.0:OSS 应用制品直传",
|
|
6
|
+
"summary": "开发工具可使用平台已配置的阿里云 OSS 直接上传应用构建包及镜像分块,服务器校验后按原摘要和进度导入,减轻客户 VPN 的大文件传输压力。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"新增独立 artifact-transfer/v1 能力协商,平台启用后自动使用限时、精确对象范围的签名直传。",
|
|
9
|
+
"镜像沿用原 OCI 摘要、预算、断点及受管仓库,已有 Registry 层在直传前复用。",
|
|
10
|
+
"平台存储设置支持前端 OSS/CDN 静态分发;登录、HTML 及 API 入口保持平台地址。"
|
|
11
|
+
],
|
|
12
|
+
"fixes": [
|
|
13
|
+
"同时收录本次物化前主线已有 Changeset:按真实构建输入复用后端镜像、HTTP 环境浏览器 SHA-256、较大声明的有界容量协商。",
|
|
14
|
+
"收录主线已有标准流程页面整理、补正派生事实、补填值联动、日期辅助、提交后导航及子表展示修正。"
|
|
15
|
+
],
|
|
16
|
+
"affectedUsers": [
|
|
17
|
+
"使用 OpenXiangda V2 发布应用且平台已配置 OSS 的开发者与管理员。"
|
|
18
|
+
],
|
|
19
|
+
"upgradeSteps": [
|
|
20
|
+
"按平台正式升级入口部署配套服务器和管理界面。",
|
|
21
|
+
"将项目 openxiangda 升至 2.60.0,按锁文件安装依赖并刷新项目同版本资料。",
|
|
22
|
+
"管理员按需启用存储设置中的开发工具直传及静态分发,核验 GET/HEAD CORS 和目录权限。"
|
|
23
|
+
],
|
|
24
|
+
"knownLimitations": [
|
|
25
|
+
"首轮仅支持阿里云 OSS;COS、MinIO、旧平台及关闭开关的站点保留原通道。",
|
|
26
|
+
"OSS 分发不等于 CDN 加速;CDN 域名需要独立配置,实际性能以部署样本为准。",
|
|
27
|
+
"暂存目录建议由管理员配置 1 天生命周期,平台不会覆盖整桶生命周期或 ACL。",
|
|
28
|
+
"本次以官方 Changeset 物化主线待发包内容,未新实现上述既有流程改动;所有版本与共享编译器需按平台组合配对。"
|
|
29
|
+
],
|
|
30
|
+
"compatibility": {
|
|
31
|
+
"node": ">=24",
|
|
32
|
+
"platform": "配套平台 artifact-transfer/v1 可选接口;应用/编译器契约不变",
|
|
33
|
+
"v1": "V1不消费新增 OSS 制品传输协议。"
|
|
34
|
+
},
|
|
35
|
+
"issues": [],
|
|
36
|
+
"sha256": "1becf5ff798495bf650c87783f0714ccaa1f5dd2d1edab1b93eccfdfbea6edde",
|
|
37
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.60.0"
|
|
38
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.60.2",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.60.2:已选部门真实事实",
|
|
6
|
+
"summary": "具名后端动作可基于平台目录解析有界已选部门名称与路径,保存可信展示快照而不复制组织权限。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"新增 directory.selected-departments 能力和 selectedDepartments 声明,SDK 使用真实发起人、固定环境与动作证明读取平台目录事实。",
|
|
9
|
+
"至多50个不重复部门按输入顺序返回声明字段,整体检查缺失、删除、授权与当前 Head,并附真实数据库时间及摘要。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"需要在 V2 业务动作中保存部门名称、父级或完整路径快照的应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"先按精确平台组合部署目录能力,再锁定同版本公开工具包并刷新契约。",
|
|
17
|
+
"具名动作显式声明字段与上限,快照只作展示,实际权限和审批路由仍由平台目录及角色控制。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"本次主题仅提供当前租户未删除部门的已有目录读取范围;不引入未实现的每部门可见策略。",
|
|
21
|
+
"无学校真实角色或页面验收声明;source/SDK聚焦测试不代替上线业务验证。"
|
|
22
|
+
],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"platform": "directory.selected-departments 1.0.0 与配套contracts/devkit/nest",
|
|
26
|
+
"v1": "V1 API 与未声明此能力的 V2 动作保持现有行为。"
|
|
27
|
+
},
|
|
28
|
+
"issues": [],
|
|
29
|
+
"sha256": "c5897f1bec938ea57c4c4d9e04381c39bc78bf47e4dce018890d42d696bbf341",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.60.2"
|
|
31
|
+
}
|
|
@@ -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
|
+
}
|
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.7.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.7.1:修复可选后端连接开发",
|
|
6
|
+
"summary": "连接开发按应用配置启动本地 Nest,绑定平台活动应用版本与开发会话,支持已激活前端应用首次启用本地后端。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"不再要求应用手动补根目录 dev:server;使用 backend.root 包内 dev 入口。纯前端应用不启动 Nest。",
|
|
10
|
+
"补齐本地 Nest 所需活动应用版本描述;本地修改的后端使用开发会话标签,不冒充已部署镜像。",
|
|
11
|
+
"开发会话目标发生变化时停止子进程并撤销原会话,防止环境与运行时身份不一致。"
|
|
12
|
+
],
|
|
13
|
+
"affectedUsers": [
|
|
14
|
+
"使用 dev 连接平台测试环境的纯前端和按需 Nest 应用开发者。"
|
|
15
|
+
],
|
|
16
|
+
"upgradeSteps": [
|
|
17
|
+
"通过项目正式升级流程采用 openxiangda 2.7.1,刷新项目资料并重启旧 MCP 与 dev 进程。",
|
|
18
|
+
"保留根目录 dev:web,确认配置的后端包具有 dev 启动脚本。"
|
|
19
|
+
],
|
|
20
|
+
"knownLimitations": [
|
|
21
|
+
"需要平台已有激活应用版本;联调数据写入仍发生在选定远端环境。",
|
|
22
|
+
"本次修复不改变线上应用制品或生产部署。"
|
|
23
|
+
],
|
|
24
|
+
"compatibility": {
|
|
25
|
+
"node": ">=24",
|
|
26
|
+
"platform": "支持 Application v2 开发会话及活动 AppVersion 的平台"
|
|
27
|
+
},
|
|
28
|
+
"issues": [],
|
|
29
|
+
"sha256": "102d3bdfb8c717e3629dac9eac67eb37f9b50588fda3bf28c9c1930512f4bb75",
|
|
30
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.7.1"
|
|
31
|
+
}
|
|
@@ -0,0 +1,39 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.75.5",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.75.5:告警优先的应用交付与同源 contracts",
|
|
6
|
+
"summary": "应用 TEST 交付对源码托管和 AppSpec 资料采用告警优先策略,并重新发布当前主线 contracts 制品,保证平台消费的编译器字节与源码提交可核验配对。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"TEST 部署计划和发布支持显式选择 AppSpec 变更;源码托管不可用、资料就绪度或来源观察项会进入警告与发布回执,而不再阻断可继续的 TEST 交付。",
|
|
9
|
+
"生产晋级保留安全、制品完整性、准确 TEST 运行和兼容性等硬门禁,同时将可修复的资料与源码来源观察项作为可见警告。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"重新发布 openxiangda-contracts 2.95.5,使平台能够用官方 registry 制品验证当前 OpenXiangda 2.0 master 提交、纯编译器摘要和 tarball 完整性。",
|
|
13
|
+
"根包、CLI、MCP 与 devkit-core 的版本发布保持同一 Changesets 发布单元,避免 CLI 模板与根包版本脱节。",
|
|
14
|
+
"富文本受控字段在父表单暂时未回传最新值时保留编辑器输入,避免工具栏操作触发内容清空。",
|
|
15
|
+
"全屏编辑切换后显式折叠非空选区的 End 键,避免后续表情或内联内容插入替换整段正文。"
|
|
16
|
+
],
|
|
17
|
+
"affectedUsers": [
|
|
18
|
+
"需要在源码托管服务暂时不可用时继续进行 OpenXiangda V2 TEST 交付的应用开发者。",
|
|
19
|
+
"维护 OpenXiangda V2 平台配套、需要消费同源公开 contracts 制品的发布维护者。"
|
|
20
|
+
],
|
|
21
|
+
"compatibility": {
|
|
22
|
+
"node": "Node.js 24 or newer for maintained toolchain",
|
|
23
|
+
"generation": "OpenXiangda V2; V1 unchanged",
|
|
24
|
+
"platform": "平台服务端须消费 openxiangda-contracts 2.95.5 官方 archive,并通过来源提交、native compiler 摘要和锁文件完整性校验。",
|
|
25
|
+
"releaseChannels": "latest / stable-v2:V2 正式版;legacy-v1:V1 维护版;alpha:预发布。"
|
|
26
|
+
},
|
|
27
|
+
"upgradeSteps": [
|
|
28
|
+
"先发布并读回同一主线提交生成的 openxiangda-contracts 2.95.5,再将平台 server 的 vendor archive、来源回执和 pnpm 锁文件同步到该版本。",
|
|
29
|
+
"应用 TEST 交付可以继续使用 warning-first 诊断;安全、制品完整性、精确运行和兼容性错误仍需修复后才能继续。",
|
|
30
|
+
"在目标测试环境分别验证 HTTP 运行健康、角色访问、发布回执和实际业务操作;包发布不代表平台部署或业务验收完成。"
|
|
31
|
+
],
|
|
32
|
+
"knownLimitations": [
|
|
33
|
+
"告警优先只放宽源码托管和 AppSpec 资料类观察项,不放宽安全、完整性、身份、权限、运行时健康或错误目标等硬门禁。",
|
|
34
|
+
"contracts npm 发布、平台镜像部署、应用 TEST 发布和真实业务验收仍是独立证据;本版本不自动修改生产应用。"
|
|
35
|
+
],
|
|
36
|
+
"issues": [],
|
|
37
|
+
"sha256": "eea400d6abfec91346f13b76ebc525b4b7e82d79e635f27dffa10d4f2d5d643c",
|
|
38
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.75.5"
|
|
39
|
+
}
|
|
@@ -0,0 +1,32 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.8.0",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.8.0:审计信息读取权限",
|
|
6
|
+
"summary": "模型声明审计信息读取权限,统一保护记录元数据、查询和变更历史。",
|
|
7
|
+
"newFeatures": [
|
|
8
|
+
"模型及直接资源可声明 audit.read,使用现有能力和角色成员权限控制四个审计元数据字段与历史读取。",
|
|
9
|
+
"标准详情页随受权记录元数据显示变更历史入口,PC 和移动端保持一致。"
|
|
10
|
+
],
|
|
11
|
+
"fixes": [
|
|
12
|
+
"修复业务字段已经受限时,创建人和更新人仍可能通过系统元数据泄露的问题。"
|
|
13
|
+
],
|
|
14
|
+
"affectedUsers": [
|
|
15
|
+
"需要对忙碌、匿名化或受限业务投影隐藏操作人身份的应用开发者。"
|
|
16
|
+
],
|
|
17
|
+
"upgradeSteps": [
|
|
18
|
+
"先部署支持 data.audit-read-access 的平台组合,再升级应用到 openxiangda 2.8.0。",
|
|
19
|
+
"在需要限制的模型声明 audit: { read: false },或声明授予管理角色的能力数组,并执行真实角色验收。"
|
|
20
|
+
],
|
|
21
|
+
"knownLimitations": [
|
|
22
|
+
"省略 audit 保留原有读取行为;应用可信后端和现有超级管理员权限保持原有语义。",
|
|
23
|
+
"受限应用启用后不可回退到忽略审计策略的后端;须保留兼容平台组合或先撤销该应用用户访问。"
|
|
24
|
+
],
|
|
25
|
+
"compatibility": {
|
|
26
|
+
"node": ">=24",
|
|
27
|
+
"platform": "声明审计读取规则需要 data.audit-read-access 1.0.0"
|
|
28
|
+
},
|
|
29
|
+
"issues": [],
|
|
30
|
+
"sha256": "be1a9505a8b3b3a1148e1f6ce4a1a34a271e7e790f1134b8b546d7146e0eb96d",
|
|
31
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.8.0"
|
|
32
|
+
}
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
{
|
|
2
|
+
"schemaVersion": "openxiangda.release-notes/v1",
|
|
3
|
+
"version": "2.8.1",
|
|
4
|
+
"status": "reviewed",
|
|
5
|
+
"title": "OpenXiangda 2.8.1:修复审计权限能力引用",
|
|
6
|
+
"summary": "审计读取策略正确复用已有能力,保留原能力定义,并拒绝缺失引用。",
|
|
7
|
+
"newFeatures": [],
|
|
8
|
+
"fixes": [
|
|
9
|
+
"修复 audit.read 引用已有管理能力时错误报告 catalog owner 冲突的问题。",
|
|
10
|
+
"本地与平台编译器一致地保留能力原定义;审计策略不再自动补建未声明能力,跨资源引用不依赖资源排序。"
|
|
11
|
+
],
|
|
12
|
+
"affectedUsers": [
|
|
13
|
+
"使用 audit.read 能力数组控制审计信息的应用开发者。"
|
|
14
|
+
],
|
|
15
|
+
"upgradeSteps": [
|
|
16
|
+
"平台采用 openxiangda-contracts 2.6.1 后,应用升级到 openxiangda 2.8.1 并重新生成和检查。",
|
|
17
|
+
"audit.read 引用现有应用能力;独立审计能力须先在 authz.capabilities 声明并按需授予角色。"
|
|
18
|
+
],
|
|
19
|
+
"knownLimitations": [
|
|
20
|
+
"省略 audit 保留原有读取行为,能力数组保持 all-of 与同一角色成员字段和行授权规则。",
|
|
21
|
+
"受限应用启用后仍须保留支持 data.audit-read-access 的兼容平台组合。"
|
|
22
|
+
],
|
|
23
|
+
"compatibility": {
|
|
24
|
+
"node": ">=24",
|
|
25
|
+
"platform": "openxiangda-contracts 2.6.1 与 data.audit-read-access 1.0.0"
|
|
26
|
+
},
|
|
27
|
+
"issues": [],
|
|
28
|
+
"sha256": "354f1883a5cbd7d5bcf32d94fbabbb4ec362df5abecec99ed78e2d687dff94b7",
|
|
29
|
+
"url": "https://github.com/1377385356/openxiangda/releases/tag/v2.8.1"
|
|
30
|
+
}
|