@mobileaidev/ai-app-bridge 0.3.0-rc.2 → 0.3.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/README.md +7 -7
- package/docs/RELEASE.md +15 -14
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -7,10 +7,10 @@ discovery. Every request checks the mapping before dispatch. Mutating requests
|
|
|
7
7
|
are never replayed after a missing route or uncertain result. For manual cleanup,
|
|
8
8
|
pass the exact serial and returned Host port to `remove-forward`.
|
|
9
9
|
|
|
10
|
-
This release
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
The supported Node range is `>=26.3.0 <27`; this
|
|
10
|
+
This release is `0.3.0`, distributed through the npm `latest` dist-tag.
|
|
11
|
+
The default installation includes the Script/Intent and capture contracts below.
|
|
12
|
+
The `next` dist-tag also points to this release until a newer candidate is published.
|
|
13
|
+
The supported Node range is `>=26.3.0 <27`; this release was checked on 26.3.0.
|
|
14
14
|
See [the release guide](docs/RELEASE.md) for local packaging and coordinated publication.
|
|
15
15
|
|
|
16
16
|
AI App Bridge CLI/MCP supports Android native apps, Android WebView/H5/CDP,
|
|
@@ -55,8 +55,8 @@ MCP exposes exactly two tools: call `capabilities` to discover
|
|
|
55
55
|
domains, commands, and options, then call `run` with the selected command.
|
|
56
56
|
|
|
57
57
|
```bash
|
|
58
|
-
#
|
|
59
|
-
npm install -g @mobileaidev/ai-app-bridge@0.3.0
|
|
58
|
+
# Install the current stable release; see docs/RELEASE.md for packaging.
|
|
59
|
+
npm install -g @mobileaidev/ai-app-bridge@0.3.0
|
|
60
60
|
|
|
61
61
|
ai-app-bridge status --package-name io.github.mobileaidev.aiappbridge.sample
|
|
62
62
|
ai-app-bridge tree --package-name io.github.mobileaidev.aiappbridge.sample
|
|
@@ -264,7 +264,7 @@ describes hashes, source binding, retention and the excluded external payloads.
|
|
|
264
264
|
- `committed` means that the fact writer has made the record readable. The
|
|
265
265
|
mobile store uses group flushing; this does not promise survival of an
|
|
266
266
|
arbitrary power loss before flush. Cold disk reads and cache performance
|
|
267
|
-
are measured separately; this
|
|
267
|
+
are measured separately; this release has not passed the old hot-query
|
|
268
268
|
latency target on all devices and retained-store sizes.
|
|
269
269
|
|
|
270
270
|
Script defaults to `restartPolicy: "none"`. Opt into `"checkpoint"` only for
|
package/docs/RELEASE.md
CHANGED
|
@@ -1,17 +1,17 @@
|
|
|
1
|
-
# 0.3.0
|
|
1
|
+
# 0.3.0 发行与接入交接
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
本文件记录正式版的依赖关系和出仓库交付入口。封版要求是同一提交的源码、发行包与公开接入合同一致；单个样本的测试进度不改变包版本或发布状态。推送 Git、创建远端标签及发布 npm/pub 包由维护者执行。
|
|
4
4
|
|
|
5
5
|
## 版本与消费方式
|
|
6
6
|
|
|
7
|
-
| 交付物 |
|
|
7
|
+
| 交付物 | 发行版本 | 独立消费入口 | 发布依赖 |
|
|
8
8
|
| --- | --- | --- | --- |
|
|
9
|
-
| Android SDK | `0.3.0
|
|
10
|
-
| Android Gradle 插件 | `0.3.0
|
|
11
|
-
| 原生 iOS SDK | Git tag `0.3.0
|
|
12
|
-
| Flutter 插件 | `0.3.0
|
|
13
|
-
| Desktop CLI/MCP | `0.3.0
|
|
14
|
-
| Web SDK | `0.3.0
|
|
9
|
+
| Android SDK | `0.3.0` | JitPack `com.github.mobileAiDev.ai-app-bridge:ai-app-bridge-android:0.3.0` | 同名 Git tag，JitPack 对该提交成功构建 |
|
|
10
|
+
| Android Gradle 插件 | `0.3.0` | JitPack `ai-app-bridge-gradle-plugin` 模块及插件 ID `io.github.mobileaidev.aiappbridge.android` | 与 SDK 相同的 Git tag；不再使用旧默认 `0.2.8` |
|
|
11
|
+
| 原生 iOS SDK | Git tag `0.3.0` | Git URL 的仓库根 `Package.swift`，产品 `AiAppBridgeIOS` | 根清单包含 Swift runtime、C adapter 和 segmented C store，无外部 C 包路径 |
|
|
12
|
+
| Flutter 插件 | `0.3.0` | pub `ai_app_bridge_flutter` | Android 固定依赖上述 SDK；iOS Swift/C 源码随插件分发 |
|
|
13
|
+
| Desktop CLI/MCP | `0.3.0` | npm `@mobileaidev/ai-app-bridge` | 包含 UIA bundle、WDA 模板和 native store 源码；WDA 上游固定 `14.1.1` |
|
|
14
|
+
| Web SDK | `0.3.0` | npm `@mobileaidev/ai-app-bridge-web` | 独立浏览器源码包，无 npm 对 CLI 的安装依赖 |
|
|
15
15
|
| Native store | `0.1.0` | 随 CLI 的 bundled dependency 安装 | 不要求另行发布到 npm；`file:../../native/segmented-fact-store` 是工作区构建入口，最终 tarball 必须包含该依赖源码 |
|
|
16
16
|
|
|
17
17
|
Flutter 的 podspec 是随 pub 插件消费的本地 podspec，不是独立 CocoaPods trunk 发布包；原生 iOS 使用根 Swift package。Flutter SwiftPM 的 `../FlutterFramework` 由 Flutter 的集成生成，不能当作本仓库的外部私有依赖，也不应将本机 Flutter framework 打包进插件。
|
|
@@ -20,13 +20,14 @@ Host 支持范围声明为 Node `>=26.3.0 <27`，本轮实际验证基线是 **2
|
|
|
20
20
|
|
|
21
21
|
## 发布顺序
|
|
22
22
|
|
|
23
|
-
1. 完成源码审阅并冻结一个提交，核对以下命令的产物确实来自它；包含当前 untracked
|
|
24
|
-
2. 维护者推送提交与 `0.3.0
|
|
23
|
+
1. 完成源码审阅并冻结一个提交，核对以下命令的产物确实来自它；包含当前 untracked 的实际源码、测试和文档，排除本机生成目录。所有对外发行版本使用同一个 `0.3.0`，若需要改版本，先同时更新上表涉及的 manifest 与固定依赖。
|
|
24
|
+
2. 维护者推送提交与 `0.3.0` 标签，让 JitPack 构建 Android SDK/插件。确认两条公开坐标可解析后，再发布依赖它们的 Flutter 包。本地 Gradle project/path/AAR 替换不能证明 JitPack 坐标可消费。
|
|
25
25
|
3. 原生 iOS 消费相同 Git tag 的根 package；完成根 package 的 iOS 构建，不仅构建 `ios/ai-app-bridge-ios/Package.swift`。Flutter iOS 则检查实际 pub 包内 Swift/C 源码与声明相符。
|
|
26
|
-
4. CLI 与 Web SDK 可分别发布到 npm
|
|
27
|
-
5.
|
|
26
|
+
4. CLI 与 Web SDK 可分别发布到 npm 的 `latest` dist-tag。CLI 的 native store 已打包随行，不等待一个不存在的单独 registry 依赖。Flutter 包发布以第 2 步完成为前提。
|
|
27
|
+
5. 同步 npm `next` 指向 `0.3.0`，让已有候选入口也使用本次正式版。将 GitHub `main` 与发行提交同步，并创建非预发布的 GitHub Release。
|
|
28
|
+
6. 从 registry/tag 安装刚发布的确切版本，读取 `capabilities` 和版本，核对来源及支持范围，确认默认安装入口指向本次发行版本。正式发布不自动等于全平台生产验收完成。
|
|
28
29
|
|
|
29
|
-
|
|
30
|
+
正式发布命令需在对应目录由维护者执行，例如 npm 使用 `npm publish --tag latest`；pub 使用 `flutter pub publish`。这些命令属于发布动作，不能混入本地验证脚本。
|
|
30
31
|
|
|
31
32
|
## 本地检查与最终包验证
|
|
32
33
|
|
package/package.json
CHANGED