diff --git a/CHANGELOG.md b/CHANGELOG.md index ef2f4921..45942602 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,6 +16,70 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). The GitHub Release body is extracted from this file: everything between the release's `## [vX.Y.Z]` heading and the next `## [` heading. Keep that section self-contained. +## [v0.3.4] - 2026-11-13 + +Console settings release. It refreshes the Console settings experience added around 0.3 +without changing the 29-tool MCP surface, graph/event/sync formats, host adapters or stored +data. There is no migration. + +### Added + +- **Settings v2 shell** — a 760×720 settings modal (760×680 for About device) with a 160px + left rail on desktop, a horizontal tab strip at 900px and below, and a full-screen layout + on narrow screens. The six sections are General, Security, Memory, Integrations, MCP and + Advanced; About device is a separate entry. +- **Memory and integration IA** — the Memory section now owns the memory mode, model source, + runtime status and model status; Integrations owns Agent configuration. Memory mode is a + compact segmented control, with long explanations kept out of the layout. +- **Consistent settings rows** — 40/58px row templates, a 150/1fr/68 field grid, 27px + controls, grouped panels, three 114px security cards, always-visible configured/effective/ + reason warning rows, and an About device page with three groups and three folds. +- **Responsive, accessible and bilingual coverage** — layout baselines at 1440/1024/900/390, + English and Chinese copy, reduced-motion behavior, settings deep links, fixed-position + service menu, focus return, and expanded Console UI smoke assertions. +- **CI reliability** — Windows-only bounded test retries, a slower local sidecar health + probe, a regression test for delayed health responses, and retry-safe Windows temp-file + cleanup. These are test/infrastructure changes, not new product capabilities. + +### Changed + +- Settings tabs now use **集成 / Integrations** (formerly AI 助手 / Assistants) and + **记忆 / Memory** (formerly 记忆运行时 / runtime), while the underlying agent and runtime + configuration remains compatible. +- The settings shell no longer scrolls as a whole: the header and rail stay fixed and only + the content column scrolls. Rows remain single-line at 900px and stack cleanly on mobile. +- Routine settings hints are carried by group/control `title` text; only actionable + warnings, pending restarts and security exceptions stay visible in the layout. +- The public MCP tool count, CLI commands, graph/event/sync formats and data layout are + unchanged. This is a Console-only release. + +### Fixed + +- **Settings tab overflow** — the expanded English tab set no longer overflows the settings + strip by 5px at 1440/1024. +- **Truthful dormant states** — sidecar tests accept `mcp/degraded` when a clean drain cannot + be confirmed, while still asserting no new writes, no outbox flush, `409 mode_mismatch` + and correct resume behavior. +- **Slow-health false 503s** — a 200ms local health probe could mark a busy sidecar + unavailable; the timeout is now 1000ms and covered by a 300ms regression test. +- **Windows cleanup races** — provisioning harness cleanup is bounded-retry and best-effort, + so a transient file lock no longer fails the suite; Windows timing-sensitive tests retry + at most twice while persistent failures still fail. +- **Settings smoke assertions** — aligned with the current IA (`Integrations`, `Add agent`, + active tab order) and the updated security/about layout. + +### Verification + +- Main CI run `43376114600` passed Linux build/test/lint (including Console UI smoke), + Windows build/test/lint, DSH E2E, desktop smoke, semantic recall and WAN NAT. +- Packaging dry-run run `43377170059` passed verify, the eight npm tarballs, Hermes bundle, + macOS/Windows/Linux desktop builds and the full DSH E2E matrix. Publish, visibility and + GitHub Release were correctly skipped; no registry or Release mutation occurred. +- `verify:console` passed; the headless Console UI smoke covers the settings v2 layout, + security cards, About device, responsive breakpoints, bilingual copy and reduced motion. +- The formal `release/v0.3.4` run reruns the same gate before publishing. Desktop packages + remain unsigned. + ## [v0.3.2] - 2026-11-06 Memory Runtime stability release. It makes lifecycle, local data, detail evidence, diff --git a/README.md b/README.md index e7d5e970..2d5f2601 100644 --- a/README.md +++ b/README.md @@ -72,14 +72,14 @@ Memory and tasks stay on your devices; devices sync directly. - + - +
Desktop app · v0.3.2Desktop app · v0.3.4 Download & first launch
Unsigned release
macOS Universal · Windows x64 · Linux x64
Download from GitHub Releases
Verify with SHA256SUMS.txt. macOS: right-click → Open. Windows: More info → Run anyway. Bundles Electron and its runtime.
Download from GitHub Releases
Verify with SHA256SUMS.txt. macOS: right-click → Open. Windows: More info → Run anyway. Bundles Electron and its runtime.
@@ -146,7 +146,7 @@ mebular print-config --client opencode # MCP config

Use with DSH
Install the plugin from npm into DSH's web profile:
-dsh plugin --profile web add @mebular/dsh-plugin@0.3.2
+dsh plugin --profile web add @mebular/dsh-plugin@0.3.4
The App and the DSH Plugin are two equal entries to one local Mebular runtime: the plugin defaults to attach and connects to an existing App/CLI/service without starting or downloading anything. If no runtime exists, the panel explicitly offers a pinned shared-runtime install. The sidebar panel embeds the same Console through ?embed=dsh (loopback only), and the official MCP client reaches the same graph. The plugin is an independent adapter with its code isolated in packages/dsh-plugin; it is published by its own npm job, while its version follows the unified release train. For plugin development, install from packages/dsh-plugin instead.
Listed on awesome-dsh-plugin under memory.
DSH plugin guide → · Integration notes →

@@ -183,6 +183,6 @@ Runnable examples: [`examples/quickstart`](examples/quickstart/index.mjs) writes
-v0.3.2 · early · MIT · © 2026 Sobert Li +v0.3.4 · early · MIT · © 2026 Sobert Li
diff --git a/README_CN.md b/README_CN.md index 947812d9..0364f6bc 100644 --- a/README_CN.md +++ b/README_CN.md @@ -72,14 +72,14 @@ - + - +
桌面 App · v0.3.2桌面 App · v0.3.4 下载与首次打开
未签名发布
macOS Universal · Windows x64 · Linux x64
从 GitHub Releases 下载
用 SHA256SUMS.txt 校验。macOS:右键 →「打开」;Windows:「更多信息 → 仍要运行」。自带 Electron 与 runtime。
从 GitHub Releases 下载
用 SHA256SUMS.txt 校验。macOS:右键 →「打开」;Windows:「更多信息 → 仍要运行」。自带 Electron 与 runtime。
@@ -146,7 +146,7 @@ mebular print-config --client opencode # MCP 配置

与 DSH 一起使用
从 npm 把插件装入 DSH 的 web profile:
-dsh plugin --profile web add @mebular/dsh-plugin@0.3.2
+dsh plugin --profile web add @mebular/dsh-plugin@0.3.4
App 与 DSH Plugin 是同一套本机 Mebular runtime 的两个等权入口:插件默认 attach,已有 App/CLI/service 时直接连接,不会启动或下载任何东西。完全没有 runtime 时,面板会先询问,再按需安装固定版本共享 runtime。侧边栏面板通过 ?embed=dsh(仅 loopback)嵌入同一套 Console,官方 MCP client 连接同一张图。插件是独立适配器,代码隔离在 packages/dsh-plugin;它由独立 npm job 发布,版本随统一 release train;开发时仍可从 packages/dsh-plugin 本地安装。
已收录于 awesome-dsh-plugin 的 memory 分类。
DSH 插件指南 → · 集成说明 →

@@ -183,6 +183,6 @@ await mebular.initialize();
-v0.3.2 · early · MIT · © 2026 Sobert Li +v0.3.4 · early · MIT · © 2026 Sobert Li
diff --git a/RELEASE.md b/RELEASE.md index 3d10671f..b3274d49 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -10,8 +10,8 @@ The release operations for this repository live under `docs/operations/`: - [Changelog](CHANGELOG.md) — release notes; the `## [vX.Y.Z]` section is the source of the GitHub Release body. -The current release line is **v0.3.2**: a single-version umbrella with eight npm packages at -`0.3.2` (`core`, `service`, `skill`, `mcp`, `fleet`, `memory-runtime`, +The current release line is **v0.3.4**: a single-version umbrella with eight npm packages at +`0.3.4` (`core`, `service`, `skill`, `mcp`, `fleet`, `memory-runtime`, `opencode-plugin`, `dsh-plugin`), and unsigned desktop installers for macOS, Windows and Linux. The DSH plugin is an isolated adapter published by its own npm job, but it follows the unified release train; no release ships the DSH plugin alone. `bump_version.sh` updates diff --git a/apps/desktop/README.md b/apps/desktop/README.md index 79a35646..802805e0 100644 --- a/apps/desktop/README.md +++ b/apps/desktop/README.md @@ -1,6 +1,6 @@ # Mebular 桌面 App(apps/desktop) -> v0.3.2:**壳 + 守护托管 + 内嵌控制台 + 发布 tarball 运行时 + 三平台 unsigned 安装包**。 +> v0.3.4:**壳 + 守护托管 + 内嵌控制台 + 发布 tarball 运行时 + 三平台 unsigned 安装包**。 > 安装包 runtime 来自与 npm 发布同一批 verify tarball;签名、公证与自动更新留到后续版本。 > 发布操作见 [`docs/operations/DESKTOP_RELEASE.md`](../../docs/operations/DESKTOP_RELEASE.md)。 @@ -13,7 +13,7 @@ Electron 薄壳:把**既有控制台**(`127.0.0.1:/console`)装进 ``` apps/desktop/ -├── package.json # private + 0.3.2(与八个 npm 包同版本) +├── package.json # private + 0.3.4(与八个 npm 包同版本) ├── electron-builder.yml # 安装包配置(runtime/node_modules → resources/node_modules) ├── runtime/ # 发布 tarball 安装出的运行时(不入库) ├── src/main/ # Electron 主进程:daemon.mjs(托管逻辑,纯可测)/ index.mjs(壳)/ ipc.mjs / tray-icons.mjs @@ -32,7 +32,7 @@ npm run dev -- --home ~/.mebular --port 7331 # 透传参数(可选) npm run smoke # 无 GUI 有界冒烟(CI 用) ``` -## 安装包(v0.3.2,unsigned) +## 安装包(v0.3.4,unsigned) 安装包里的 Mebular 运行时**不来自仓库源码目录**,而是先用 `npm pack` 产出六个发布 tarball,再由 `prepare-runtime` 一次性 `npm install --omit=dev --ignore-scripts` 到 @@ -98,7 +98,7 @@ npm run verify:desktop:assets -- \ --require-hermes ``` -> v0.3.2 产物**未签名、未公证**:macOS Gatekeeper 要求右键 → 打开(或系统设置 → 隐私与 +> v0.3.4 产物**未签名、未公证**:macOS Gatekeeper 要求右键 → 打开(或系统设置 → 隐私与 > 安全性 → 仍要打开),Windows SmartScreen 要求「更多信息 → 仍要运行」。发布前先用 > Release 的 `SHA256SUMS.txt` 校验。签名、公证与自动更新留到后续版本;完整说明见 > [`docs/operations/DESKTOP_RELEASE.md`](../../docs/operations/DESKTOP_RELEASE.md)。 diff --git a/apps/desktop/package-lock.json b/apps/desktop/package-lock.json index e053e29d..93b64833 100644 --- a/apps/desktop/package-lock.json +++ b/apps/desktop/package-lock.json @@ -1,12 +1,12 @@ { "name": "@mebular/desktop", - "version": "0.3.2", + "version": "0.3.4", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@mebular/desktop", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "devDependencies": { "electron": "42.11.18", diff --git a/apps/desktop/package.json b/apps/desktop/package.json index 27c2aa6c..042751e3 100644 --- a/apps/desktop/package.json +++ b/apps/desktop/package.json @@ -2,7 +2,7 @@ "name": "@mebular/desktop", "productName": "Mebular", "desktopName": "mebular", - "version": "0.3.2", + "version": "0.3.4", "private": true, "description": "Mebular 桌面应用(Electron 壳 + 内嵌控制台 + 守护托管)", "license": "MIT", diff --git a/apps/desktop/src/main/daemon.mjs b/apps/desktop/src/main/daemon.mjs index 8cb1607e..46b3cc6a 100644 --- a/apps/desktop/src/main/daemon.mjs +++ b/apps/desktop/src/main/daemon.mjs @@ -12,7 +12,7 @@ import { homedir } from 'node:os'; import { dirname, join, resolve } from 'node:path'; import { fileURLToPath, pathToFileURL } from 'node:url'; -export const APP_VERSION = '0.3.2'; +export const APP_VERSION = '0.3.4'; export const SERVICE_KIND = 'mebular-serve'; /** App 注册到 /runtime-providers.json 的能力(只写发现信息,不写 token/身份)。 */ export const APP_RUNTIME_PROVIDER_CAPABILITIES = Object.freeze(['serve']); diff --git a/docs/README.md b/docs/README.md index c102e71d..2c319dd5 100644 --- a/docs/README.md +++ b/docs/README.md @@ -53,7 +53,8 @@ main [`README.md`](../README.md); this index only describes document structure. [E2a2](console/screens/e2a2/README.md) · [security tiers](console/screens/security-tiers/README.md) · [U1](console/screens/u1/README.md) · - [U3](console/screens/u3/README.md) + [U3](console/screens/u3/README.md) · + [U4 settings v2](console/screens/u4-settings-redesign/README.md) ## Design @@ -66,6 +67,7 @@ main [`README.md`](../README.md); this index only describes document structure. ## Quality and release evidence +- [v0.3.4 verification](quality/0.3.4-verification.md) — Console settings redesign scope, SSOT/build/lint/docs checks and release dry-run - [v0.3.2 verification matrix](quality/0.3.2-verification.md) — final test counts, host boundaries, scale/model evidence and explicit pending items - [v0.3.2 scale benchmark](quality/0.3.2-scale-benchmark.md) — 1k/2k/10k count audits, performance, resources, failure injection and preserved 10k failure history - [v0.3.2 real-model canary](quality/0.3.2-model-smoke.md) — Qwen3-4B Q4_K_M on macOS x64 with a test-only mirror; records the default-HF failure and exact boundary diff --git a/docs/integrations/DSH.md b/docs/integrations/DSH.md index 90c00e2e..0fff13c1 100644 --- a/docs/integrations/DSH.md +++ b/docs/integrations/DSH.md @@ -36,7 +36,7 @@ resolve`/`supervise`) and daemon HTTP endpoints. Install from npm into the DSH web profile: ```bash -dsh plugin --profile web add @mebular/dsh-plugin@0.3.2 +dsh plugin --profile web add @mebular/dsh-plugin@0.3.4 ``` For development: @@ -371,10 +371,10 @@ panel header displays. If they differ, the header tooltip shows the runtime vers "runtimeMode": "reused", "managed": false, "panel": true, - "version": "0.3.2", - "pluginVersion": "0.3.2", + "version": "0.3.4", + "pluginVersion": "0.3.4", "profile": { "id": "default", "name": "My Cloud" }, - "provider": { "kind": "app", "source": "registry", "version": "0.3.2" }, + "provider": { "kind": "app", "source": "registry", "version": "0.3.4" }, "service": { "registered": false, "running": false, "foreign": false }, "downloadRequired": false, "install": { "state": "idle", "allowed": true }, @@ -483,13 +483,13 @@ single daemon, service, update locks and upgrade rollback are covered by CI and ## Release and version -- Version: `0.3.2`, on the unified Mebular v0.3.2 release train (seven lockstep npm +- Version: `0.3.4`, on the unified Mebular v0.3.4 release train (seven lockstep npm packages plus the isolated `dsh-plugin` share the same version). -- npm: `@mebular/dsh-plugin@0.3.2`. +- npm: `@mebular/dsh-plugin@0.3.4`. - The Plugin is an isolated adapter in `packages/dsh-plugin`, published by its own npm job. It reads the pinned runtime version from its own `package.json`, so a release bump needs no Plugin source edit. -- Publish `@mebular/core@0.3.2` before `@mebular/dsh-plugin@0.3.2`; see +- Publish `@mebular/core@0.3.4` before `@mebular/dsh-plugin@0.3.4`; see [Release SOP](../operations/RELEASE.md). - Listed in the `memory` category of [awesome-dsh-plugin](https://awesome-dsh-plugin.com/p/Windsander/Mebular--packages-dsh-plugin/). diff --git a/docs/integrations/DSH_CN.md b/docs/integrations/DSH_CN.md index 5015ff40..966730bd 100644 --- a/docs/integrations/DSH_CN.md +++ b/docs/integrations/DSH_CN.md @@ -31,7 +31,7 @@ supervisor 的 `runtime resolve`/`supervise` 和 daemon HTTP 端点工作。 从 npm 安装到 DSH 的 Web profile: ```bash -dsh plugin --profile web add @mebular/dsh-plugin@0.3.2 +dsh plugin --profile web add @mebular/dsh-plugin@0.3.4 ``` 开发时从工作树安装: @@ -318,10 +318,10 @@ HTTP 请求,不是整个 DSH 插件完全不注册 listener/timer。 "runtimeMode": "reused", "managed": false, "panel": true, - "version": "0.3.2", - "pluginVersion": "0.3.2", + "version": "0.3.4", + "pluginVersion": "0.3.4", "profile": { "id": "default", "name": "我的忆云" }, - "provider": { "kind": "app", "source": "registry", "version": "0.3.2" }, + "provider": { "kind": "app", "source": "registry", "version": "0.3.4" }, "service": { "registered": false, "running": false, "foreign": false }, "downloadRequired": false, "install": { "state": "idle", "allowed": true }, @@ -417,11 +417,11 @@ npm run verify:runtime:coexistence ## 发布与版本 -- 版本:`0.3.2`,随统一 Mebular v0.3.2 release train(七个 lockstep npm 包加独立的 `dsh-plugin` 同版本) -- npm:`@mebular/dsh-plugin@0.3.2` +- 版本:`0.3.4`,随统一 Mebular v0.3.4 release train(七个 lockstep npm 包加独立的 `dsh-plugin` 同版本) +- npm:`@mebular/dsh-plugin@0.3.4` - 插件是独立适配器:代码隔离在 `packages/dsh-plugin`,由独立 npm job 发布;插件运行时从 自己的 `package.json` 读取 pinned runtime 版本,发布 bump 不需要改插件源码。 -- 发布先 `@mebular/core@0.3.2`,再 `@mebular/dsh-plugin@0.3.2`;详见 +- 发布先 `@mebular/core@0.3.4`,再 `@mebular/dsh-plugin@0.3.4`;详见 [发布 SOP](../operations/RELEASE.md)。 - 插件已收录于 [awesome-dsh-plugin](https://awesome-dsh-plugin.com/zh/p/Windsander/Mebular--packages-dsh-plugin/) diff --git a/docs/integrations/HERMES.md b/docs/integrations/HERMES.md index 40bad896..1b60659f 100644 --- a/docs/integrations/HERMES.md +++ b/docs/integrations/HERMES.md @@ -97,15 +97,15 @@ when the MCP setting `memoryRuntime.enabled=true` (or when you start it manually While it is ready, `/memory-runtime.json` exists and contains the sidecar URL plus `tokenFile` (normally `/memory-runtime/host-token`). -3. Install the provider from the release bundle (available **after** the 0.3.2 +3. Install the provider from the release bundle (available **after** the 0.3.4 release; use the source command below before the release). The provider must be installed as `plugins/mebular`, because Hermes uses the directory name as the value of `memory.provider`: ```bash - gh release download v0.3.2 -p 'mebular-hermes-plugins-*.tar.gz' + gh release download v0.3.4 -p 'mebular-hermes-plugins-*.tar.gz' mkdir -p mebular-hermes-plugins - tar -xzf mebular-hermes-plugins-0.3.2.tar.gz -C mebular-hermes-plugins + tar -xzf mebular-hermes-plugins-0.3.4.tar.gz -C mebular-hermes-plugins cd mebular-hermes-plugins HERMES_HOME="${HERMES_HOME:-$HOME/.hermes}" ./install.sh diff --git a/docs/integrations/HERMES_CN.md b/docs/integrations/HERMES_CN.md index 7937eeba..31f54688 100644 --- a/docs/integrations/HERMES_CN.md +++ b/docs/integrations/HERMES_CN.md @@ -93,13 +93,13 @@ Provider 需要 0.3 Memory Runtime sidecar 正在运行。只有 MCP 设置 sidecar 就绪时存在 `/memory-runtime.json`,其中包含 sidecar URL 和 `tokenFile`(通常是 `/memory-runtime/host-token`)。 -3. 从 Release 资产安装(**0.3.2 发布后**可用;发布前用下面的源码命令)。安装目录必须叫 +3. 从 Release 资产安装(**0.3.4 发布后**可用;发布前用下面的源码命令)。安装目录必须叫 `plugins/mebular`,因为 Hermes 用目录名作为 `memory.provider` 的值: ```bash - gh release download v0.3.2 -p 'mebular-hermes-plugins-*.tar.gz' + gh release download v0.3.4 -p 'mebular-hermes-plugins-*.tar.gz' mkdir -p mebular-hermes-plugins - tar -xzf mebular-hermes-plugins-0.3.2.tar.gz -C mebular-hermes-plugins + tar -xzf mebular-hermes-plugins-0.3.4.tar.gz -C mebular-hermes-plugins cd mebular-hermes-plugins HERMES_HOME="${HERMES_HOME:-$HOME/.hermes}" ./install.sh diff --git a/docs/operations/DESKTOP_RELEASE.md b/docs/operations/DESKTOP_RELEASE.md index 81333023..18db28f2 100644 --- a/docs/operations/DESKTOP_RELEASE.md +++ b/docs/operations/DESKTOP_RELEASE.md @@ -1,16 +1,16 @@ # 桌面安装包发布 -面向 Mebular v0.3.2 的桌面安装包构建、验收与后续签名计划。发布流程总览见 +面向 Mebular v0.3.4 的桌面安装包构建、验收与后续签名计划。发布流程总览见 [`RELEASE.md`](RELEASE.md)。 -## 0. v0.3.2 范围 +## 0. v0.3.4 范围 | 平台 | 目标 | 架构 | 产物 | | --- | --- | --- | --- | -| macOS | DMG | Universal(arm64 + x64) | `Mebular-0.3.2-universal.dmg` | -| Windows | NSIS | x64 | `Mebular-Setup-0.3.2.exe` | -| Linux | AppImage | x64 | `Mebular-0.3.2-x86_64.AppImage` | -| Linux | deb | x64 | `Mebular-0.3.2-amd64.deb` | +| macOS | DMG | Universal(arm64 + x64) | `Mebular-0.3.4-universal.dmg` | +| Windows | NSIS | x64 | `Mebular-Setup-0.3.4.exe` | +| Linux | AppImage | x64 | `Mebular-0.3.4-x86_64.AppImage` | +| Linux | deb | x64 | `Mebular-0.3.4-amd64.deb` | - 全部为 **unsigned** 发布;不做代码签名、公证或自动更新。 - 每个安装包都自带 Electron 和一份完整的 Mebular runtime,**不需要本机 Node.js**,也不依赖 @@ -243,21 +243,21 @@ electron-builder 的 `artifactName` 固定为: | 平台 | 配置 | 最终文件名 | | --- | --- | --- | -| macOS | `Mebular-${version}-${arch}.${ext}` + `--universal` | `Mebular-0.3.2-universal.dmg` | -| Windows | `Mebular-Setup-${version}.${ext}` | `Mebular-Setup-0.3.2.exe` | -| Linux AppImage | `Mebular-${version}-${arch}.${ext}` + x64 | `Mebular-0.3.2-x86_64.AppImage` | -| Linux deb | 同上;deb 的 arch 宏为 `amd64` | `Mebular-0.3.2-amd64.deb` | +| macOS | `Mebular-${version}-${arch}.${ext}` + `--universal` | `Mebular-0.3.4-universal.dmg` | +| Windows | `Mebular-Setup-${version}.${ext}` | `Mebular-Setup-0.3.4.exe` | +| Linux AppImage | `Mebular-${version}-${arch}.${ext}` + x64 | `Mebular-0.3.4-x86_64.AppImage` | +| Linux deb | 同上;deb 的 arch 宏为 `amd64` | `Mebular-0.3.4-amd64.deb` | `SHA256SUMS.txt` 由 `scripts/verify-desktop-assets.mjs` 生成,覆盖 4 个安装包和 Hermes 插件 tarball,按文件名 ASCII 排序(等价 `LC_ALL=C sort`),每行 ` <文件名>`,例如: ```text - Mebular-0.3.2-amd64.deb - Mebular-0.3.2-universal.dmg - Mebular-0.3.2-x86_64.AppImage - Mebular-Setup-0.3.2.exe - mebular-hermes-plugins-0.3.2.tar.gz + Mebular-0.3.4-amd64.deb + Mebular-0.3.4-universal.dmg + Mebular-0.3.4-x86_64.AppImage + Mebular-Setup-0.3.4.exe + mebular-hermes-plugins-0.3.4.tar.gz ``` release job 直接调用该脚本(`--expect dmg,exe,AppImage,deb --require-hermes`)校验资产并 @@ -267,7 +267,7 @@ release job 直接调用该脚本(`--expect dmg,exe,AppImage,deb --require-her ## 4. unsigned 安装体验 -v0.3.2 没有 Apple Developer ID、公证或 Windows 代码签名证书。用户会看到系统安全提示, +v0.3.4 没有 Apple Developer ID、公证或 Windows 代码签名证书。用户会看到系统安全提示, 这是预期行为,不是安装包损坏。 本机 unsigned dry-run 的实测结果是:DMG 的 `hdiutil verify` 通过(压缩/分区校验和完整), @@ -298,17 +298,17 @@ Windows 可用 PowerShell 的 `Get-FileHash -Algorithm SHA256` 对照 `SHA256SUM ### 4.3 Windows SmartScreen -1. 运行 `Mebular-Setup-0.3.2.exe`。 +1. 运行 `Mebular-Setup-0.3.4.exe`。 2. 出现「Windows 已保护你的电脑」时点「更多信息」,再点「仍要运行」。 ### 4.4 Linux ```bash -chmod +x Mebular-0.3.2-x86_64.AppImage -./Mebular-0.3.2-x86_64.AppImage +chmod +x Mebular-0.3.4-x86_64.AppImage +./Mebular-0.3.4-x86_64.AppImage # Debian / Ubuntu -sudo apt install ./Mebular-0.3.2-amd64.deb +sudo apt install ./Mebular-0.3.4-amd64.deb ``` AppImage 需要 FUSE;没有 FUSE 时可使用 `--appimage-extract-and-run`。deb 安装后从应用菜单 @@ -381,7 +381,7 @@ npm run verify:desktop:assets -- \ ## 6. 签名、公证与自动更新(后续) -v0.3.2 明确不签名。后续版本的建议顺序: +v0.3.4 明确不签名。后续版本的建议顺序: 1. **macOS**:申请 Developer ID Application 证书;在 CI 注入 `CSC_LINK` / `CSC_KEY_PASSWORD`,移除 `electron-builder.yml` 的 `identity: null`;用 @@ -406,7 +406,7 @@ v0.3.2 明确不签名。后续版本的建议顺序: | `runtime 缺少必需文件` | 根包 `files` 或构建产物不完整;先 `npm run build`,再重新 pack。 | | `dist:mac` 失败并提示架构 / 证书 | Universal 只能在 macOS 构建;`identity: null` 下不应要求证书。 | | `dist:*` 提示找不到 Electron / `electron/dist` 为空 | npm 11.19+ 默认阻止依赖安装脚本;执行 `node apps/desktop/node_modules/electron/install.js`,确认 `path.txt` 与 `dist/` 已生成后重试。 | -| `codesign --verify` 报 `code object is not signed at all` | v0.3.2 预期 unsigned;只要 `hdiutil verify` 通过、sha256 匹配即可。不要伪造签名。 | +| `codesign --verify` 报 `code object is not signed at all` | v0.3.4 预期 unsigned;只要 `hdiutil verify` 通过、sha256 匹配即可。不要伪造签名。 | | `spctl` 报 `rejected / no usable signature` | Gatekeeper 对未签名包的预期结果;按 4.2 右键打开,或交由后续版本签名/公证。 | | `verify:desktop:assets` 报「dmg 恰好 1 个」失败 | `dist/` 里混入了旧产物;清空 `apps/desktop/dist` 后重新构建。 | | packaged smoke 找不到 `Resources` | 查看 `apps/desktop/dist/` 实际目录;不同 electron-builder 版本的解包目录名可能不同。 | diff --git a/docs/operations/RELEASE.md b/docs/operations/RELEASE.md index 9993dfbe..d6784f63 100644 --- a/docs/operations/RELEASE.md +++ b/docs/operations/RELEASE.md @@ -3,9 +3,9 @@ 面向 `@mebular/*` npm 包与三平台桌面安装包的发布操作手册。核心约束:**分支名即版本号 (SSOT)**、**先构建安装包再发 npm**、**幂等发布**、**按 ref 串行**。 -当前发布线 v0.3.2: +当前发布线 v0.3.4: -- **8 个 npm 包**统一为 `0.3.2`(单版本 umbrella):`core` / `service` / `skill` / `mcp` / +- **8 个 npm 包**统一为 `0.3.4`(单版本 umbrella):`core` / `service` / `skill` / `mcp` / `fleet` / `memory-runtime` / `opencode-plugin` 七个 lockstep 包,加独立 npm job 的 `dsh-plugin`; - macOS Universal DMG、Windows NSIS x64、Linux AppImage + deb x64(unsigned); @@ -61,7 +61,7 @@ v0.3.0 也新增独立的 `@mebular/opencode-plugin`(OpenCode V2 / OpenChamber `MEBULAR_MEMORY_RUNTIME_BIN` > 包内捆绑路径 > `PATH` 解析。 - **桌面版本**:`apps/desktop/package.json`、`apps/desktop/package-lock.json` 与 `apps/desktop/src/main/daemon.mjs` 的 `APP_VERSION` 必须等于发布版本。 -- **触发方式**:push 到 `release/v*` 分支(例如 `release/v0.3.2`),**不使用 tag 触发**。 +- **触发方式**:push 到 `release/v*` 分支(例如 `release/v0.3.4`),**不使用 tag 触发**。 手动 `workflow_dispatch` 是 packaging dry-run。 - **发布分支即真相**:`release/vX.Y.Z` 的 `X.Y.Z` 必须等于 8 个 `package.json` 的版本、 根 `package-lock.json` 的 workspace 条目、桌面三处版本、MCP 版本源、sidecar @@ -109,24 +109,24 @@ v0.3.0 也新增独立的 `@mebular/opencode-plugin`(OpenCode V2 / OpenChamber - **npm unpublish(72 小时窗口)**:仅能删除**发布后 72 小时内**、且**无人依赖**的版本; 超时或被依赖一律 400。八个包各执行一次(同一版本): ```bash - npm unpublish @mebular/core@0.3.2 # 重复 core → service → memory-runtime → skill → mcp → fleet → opencode-plugin → dsh-plugin + npm unpublish @mebular/core@0.3.4 # 重复 core → service → memory-runtime → skill → mcp → fleet → opencode-plugin → dsh-plugin ``` 同一版本被删除后**不可再以相同版本号重新发布**,后续必须升号。 - **npm deprecate(常规手段)**:标记问题版本,安装时会打印警告但不阻断: ```bash - npm deprecate @mebular/mcp@0.3.2 "broken: upgrade to a newer version" + npm deprecate @mebular/mcp@0.3.4 "broken: upgrade to a newer version" ``` 建议八个包用同一条消息一并废弃,再发布更高修复版本。 - **回退 GitHub Release**: ```bash - gh release delete v0.3.2 --yes # 仅删 Release - git push origin :refs/tags/v0.3.2 # 删除 tag(仅在确认无人依赖时) + gh release delete v0.3.4 --yes # 仅删 Release + git push origin :refs/tags/v0.3.4 # 删除 tag(仅在确认无人依赖时) ``` 或网页端 Releases → 该版本 → Delete release;若只想隐藏,标为 **pre-release**。 注意:删除 Release 不会撤销 npm 发布,npm 仍需按上面的步骤处理。 - **只换安装包**:npm 不受影响。重新构建后对同一 tag 重传资产即可: ```bash - gh release upload v0.3.2 release-assets/* --clobber + gh release upload v0.3.4 release-assets/* --clobber ``` 下载页会立即使用新文件;`SHA256SUMS.txt` 必须与安装包一起重传。 @@ -223,24 +223,24 @@ origin/main ```bash git fetch origin -git switch -c release-prep/v0.3.2 origin/main # 先 prep,dry-run 后再建 release 分支 -bash scripts/bump_version.sh v0.3.2 # 同步 8 包 + 版本源 + CHANGELOG 章节 +git switch -c release-prep/v0.3.4 origin/main # 先 prep,dry-run 后再建 release 分支 +bash scripts/bump_version.sh v0.3.4 # 同步 8 包 + 版本源 + CHANGELOG 章节 npm run verify:release-version # 只读校验;也可带 --version/--tag ``` `bump_version.sh` 会: 1. 将 8 个 `package.json`(core / fleet / mcp / memory-runtime / service / skill / - opencode-plugin / dsh-plugin)改为 `0.3.2`; + opencode-plugin / dsh-plugin)改为 `0.3.4`; 2. 同步根 `package-lock.json` 的根版本与 8 个 workspace 条目; 3. 同步桌面 `package.json` / `package-lock.json` / `APP_VERSION`; -4. 同步任何「已是版本号区间」的内部 `@mebular/*` 依赖为 `^0.3.2`; +4. 同步任何「已是版本号区间」的内部 `@mebular/*` 依赖为 `^0.3.4`; 5. 改写 `packages/mcp/src/version.mjs` 的 `APP_VERSION`(MCP 唯一版本源)、 `packages/memory-runtime/src/sidecar/config.ts` 的 `SIDECAR_RUNTIME_VERSION` (sidecar 唯一版本源)与 `packages/opencode-plugin/index.js` 的 `PACKAGE_VERSION`; -6. 在 `CHANGELOG.md` 顶部插入 `## [v0.3.2] - ` 章节(已存在则跳过,幂等)。 +6. 在 `CHANGELOG.md` 顶部插入 `## [v0.3.4] - ` 章节(已存在则跳过,幂等)。 -> 若版本号与 CHANGELOG 章节已存在(例如当前 `release-prep/v0.3.2`),**不需要**再跑 +> 若版本号与 CHANGELOG 章节已存在(例如当前 `release-prep/v0.3.4`),**不需要**再跑 > `bump_version.sh`;只有从新版本开始时才执行上面的 bump。 ### 3.2 本地预检(推荐) @@ -288,7 +288,7 @@ node --experimental-vm-modules node_modules/jest/bin/jest.js \ 发布后可见性 gate 也可以独立预演(对已发布版本只读): ```bash -npm run verify:release-visibility -- --version 0.3.2 --timeout-seconds 60 --interval-seconds 5 +npm run verify:release-visibility -- --version 0.3.4 --timeout-seconds 60 --interval-seconds 5 ``` 桌面链路(与 CI 同路径): @@ -342,7 +342,7 @@ DSH 破坏”。 ```bash # 在 release-prep 分支上触发(workflow 已在 main 注册) -gh workflow run publish.yml --ref release-prep/v0.3.2 +gh workflow run publish.yml --ref release-prep/v0.3.4 # 观察 gh run list --workflow=publish.yml --limit 5 @@ -374,9 +374,9 @@ sha256sum release-assets/* # Linux dry-run 通过后,从 prep 分支创建正式发布分支并 push: ```bash -git switch release-prep/v0.3.2 -git switch -c release/v0.3.2 -git push -u origin release/v0.3.2 +git switch release-prep/v0.3.4 +git switch -c release/v0.3.4 +git push -u origin release/v0.3.4 ``` push 后自动执行第 2 节的完整流水线。任一 job 失败即停;安装包未全绿时不会发 npm; @@ -385,7 +385,7 @@ push 后自动执行第 2 节的完整流水线。任一 job 失败即停;安 ### 5.2 观察 ```bash -gh run list --workflow=publish.yml --branch release/v0.3.2 --limit 5 +gh run list --workflow=publish.yml --branch release/v0.3.4 --limit 5 gh run watch gh run view --log-failed # 失败时 @@ -398,19 +398,19 @@ gh run view --json jobs --jq '.jobs[] | select(.name | contains("visibi ```bash # npm 八包:version 与 latest 都必须指向本次版本 for p in core service skill mcp fleet memory-runtime opencode-plugin dsh-plugin; do - npm view "@mebular/$p@0.3.2" version + npm view "@mebular/$p@0.3.4" version npm view "@mebular/$p" dist-tags.latest done # 或复用流水线同一个 gate(只读轮询;已可见时立即通过) -npm run verify:release-visibility -- --version 0.3.2 --dsh-version 0.3.2 +npm run verify:release-visibility -- --version 0.3.4 --dsh-version 0.3.4 # GitHub Release -gh release view v0.3.2 -gh release view v0.3.2 --json assets --jq '.assets[] | "\(.name) \(.size) bytes"' +gh release view v0.3.4 +gh release view v0.3.4 --json assets --jq '.assets[] | "\(.name) \(.size) bytes"' # 根包双 bin + sidecar 包 -npm install -g @mebular/core@0.3.2 @mebular/memory-runtime@0.3.2 +npm install -g @mebular/core@0.3.4 @mebular/memory-runtime@0.3.4 command -v mebular && command -v fleet && command -v mebular-memory-runtime mebular tools >/dev/null && fleet --version mebular-memory-runtime version @@ -428,13 +428,13 @@ mebular-memory-runtime version 插件 tarball(至少 5 行); - [ ] `release/vX.Y.Z` 已通过 PR 回合并 `main`,随后删除 release / prep 分支。 -> 不要用 `npm install -g @mebular/mcp@0.3.2` 冒充双 bin 安装:`@mebular/mcp` 只提供 +> 不要用 `npm install -g @mebular/mcp@0.3.4` 冒充双 bin 安装:`@mebular/mcp` 只提供 > `mebular`,`fleet` 必须来自根包(或单独安装 `@mebular/fleet`)。 插件独立验证(先让 App / 守护运行): ```bash -dsh plugin --profile web add @mebular/dsh-plugin@0.3.2 +dsh plugin --profile web add @mebular/dsh-plugin@0.3.4 dsh --profile web --dump-config | grep -A3 mebular # host row;transport 由官方 MCP client 挂载 # DSH 会话中确认 mcp__mebular__* 可调用;侧边栏面板加载 /console/?embed=dsh ``` @@ -456,7 +456,7 @@ MEBULAR_HOME="$(mktemp -d)" mebular serve --port 7399 从 Release 下载并校验: ```bash -gh release download v0.3.2 -D release-assets +gh release download v0.3.4 -D release-assets cd release-assets # Linux @@ -482,7 +482,7 @@ Get-Content SHA256SUMS.txt | ForEach-Object { - macOS 打开 DMG 后能启动;Windows NSIS 能安装并启动;Linux AppImage 可执行,deb 可安装; - 首次启动能进入锁定控制台,`/healthz` 正常; - 全部为 **unsigned** 发布:macOS Gatekeeper 与 Windows SmartScreen 会拦截,按 Release - notes 的绕过步骤操作。签名、公证与自动更新不在 v0.3.2 范围。 + notes 的绕过步骤操作。签名、公证与自动更新不在 v0.3.4 范围。 Hermes 插件 tarball 的离线验收(用临时 `HERMES_HOME`,不碰真实 `~/.hermes`): @@ -596,7 +596,7 @@ node scripts/prune-merged-branches.mjs --apply --yes # 确认后删除 发布分支本身在回合并 main 后,再用同一脚本或显式命令删除: ```bash -git push origin --delete release/v0.3.2 release-prep/v0.3.2 +git push origin --delete release/v0.3.4 release-prep/v0.3.4 ``` > 不要未经确认批量删除;不要删除 `site-*`(Pages 部署源)或仍有 open PR 的分支。 diff --git a/docs/quality/0.3.4-verification.md b/docs/quality/0.3.4-verification.md new file mode 100644 index 00000000..38beeb92 --- /dev/null +++ b/docs/quality/0.3.4-verification.md @@ -0,0 +1,45 @@ +# Mebular v0.3.4 verification matrix + +**Status:** Release-prep candidate, 2026-11-13. The packaging dry-run passed; formal +`release/v0.3.4` publication is pending explicit confirmation. + +**Scope:** Console settings IA and settings-modal redesign (#314, #315), plus the Windows/CI +reliability changes in #313, #316 and #317. The 29-tool MCP surface, graph/event/sync formats, +host adapters and stored data are unchanged. There is no migration. + +## UI and compatibility checks + +- Settings v2 shell: 760×720 settings / 760×680 About device, 160px desktop rail, + horizontal tabs at 900px and below, full-screen at narrow widths. +- Six sections: General, Security, Memory, Integrations, MCP, Advanced; About device is a + separate entry. +- Settings rows: 40/58px templates, 150/1fr/68 field grid, 27px controls, grouped panels, + security cards, visible configured/effective/reason warnings, and three About folds. +- Responsive baselines at 1440/1024/900/390; English and Chinese copy; reduced-motion; + settings deep links; focus return and fixed-position service menu. +- Existing public MCP tool count (29), CLI surface and data formats are unchanged. + +## Verification + +- `npm run verify:release-version` — passed for eight packages, root/desktop locks, MCP, + sidecar, OpenCode, Hermes manifests and the `v0.3.4` CHANGELOG section. +- `npm run build` — passed. +- `npm run lint` — passed. +- `npm run check:docs` / `check:i18n` / `check:deps` — passed. +- Main CI on `a558e8e` — run `43376114600` passed Linux build/test/lint (including Console UI + smoke), Windows build/test/lint, DSH E2E, desktop smoke, semantic recall and WAN NAT. +- Packaging dry-run — run `43377170059` on `release-prep/v0.3.4` (`db1c4bf`) passed verify, + the eight npm tarballs, Hermes bundle, macOS/Windows/Linux desktop builds and the full DSH + E2E matrix. `preflight`, npm publish, visibility and GitHub Release were correctly skipped; + no registry or Release mutation occurred. +- Console UI smoke and the full Jest suite passed in the clean CI runners. The formal release + branch reruns the same gate before publishing. + +## Known boundaries + +- Desktop packages remain unsigned; macOS Gatekeeper and Windows SmartScreen confirmation + are required. Auto-update is not included. +- This is a Console-only release. It does not add MCP tools, host adapters, model sources or + graph/event/sync changes. +- The settings redesign is a visual/IA change; existing configuration paths and APIs remain + compatible. diff --git a/integrations/hermes/README.md b/integrations/hermes/README.md index 425206fc..3680b41f 100644 --- a/integrations/hermes/README.md +++ b/integrations/hermes/README.md @@ -25,15 +25,15 @@ ## 一键安装(Release 资产) -> 0.3.2 发布后,下面的 GitHub Release 资产可用。发布前或从源码开发时,使用文末的“源码安装”。 +> 0.3.4 发布后,下面的 GitHub Release 资产可用。发布前或从源码开发时,使用文末的“源码安装”。 发布后,GitHub Release 会提供 `mebular-hermes-plugins-.tar.gz`,与 npm 包使用同一版本号。不需要 PyPI,也不需要手工查找 `$HERMES_HOME`: ```bash -# 1) 下载并解压(示例版本 0.3.2) -gh release download v0.3.2 -p 'mebular-hermes-plugins-*.tar.gz' +# 1) 下载并解压(示例版本 0.3.4) +gh release download v0.3.4 -p 'mebular-hermes-plugins-*.tar.gz' mkdir -p mebular-hermes-plugins -tar -xzf mebular-hermes-plugins-0.3.2.tar.gz -C mebular-hermes-plugins +tar -xzf mebular-hermes-plugins-0.3.4.tar.gz -C mebular-hermes-plugins cd mebular-hermes-plugins # 2) 安装到 $HERMES_HOME/plugins(默认 ~/.hermes/plugins) diff --git a/integrations/hermes/mebular-companion/plugin.yaml b/integrations/hermes/mebular-companion/plugin.yaml index dd364e24..573b3aec 100644 --- a/integrations/hermes/mebular-companion/plugin.yaml +++ b/integrations/hermes/mebular-companion/plugin.yaml @@ -1,5 +1,5 @@ name: mebular-companion -version: 0.3.2 +version: 0.3.4 description: "Optional Mebular companion — host-model memory candidate extraction via ctx.llm (not a memory provider)." kind: standalone provides_hooks: diff --git a/integrations/hermes/mebular-memory/plugin.yaml b/integrations/hermes/mebular-memory/plugin.yaml index 0245a330..353b6ae1 100644 --- a/integrations/hermes/mebular-memory/plugin.yaml +++ b/integrations/hermes/mebular-memory/plugin.yaml @@ -1,3 +1,3 @@ name: mebular -version: 0.3.2 +version: 0.3.4 description: "Mebular memory runtime provider — cross-device recall and durable transcript ingest for Hermes Agent." diff --git a/package-lock.json b/package-lock.json index 0cc0f570..b3681e60 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@mebular/core", - "version": "0.3.2", + "version": "0.3.4", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@mebular/core", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "workspaces": [ "packages/*" @@ -9099,7 +9099,7 @@ }, "packages/dsh-plugin": { "name": "@mebular/dsh-plugin", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "engines": { "dsh": ">=0.2.1-rc.2 <0.3.0", @@ -9111,7 +9111,7 @@ }, "packages/fleet": { "name": "@mebular/fleet", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "dependencies": { "@mebular/core": "file:../..", @@ -9127,7 +9127,7 @@ }, "packages/mcp": { "name": "@mebular/mcp", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "dependencies": { "@mebular/core": "file:../..", @@ -9145,7 +9145,7 @@ }, "packages/memory-runtime": { "name": "@mebular/memory-runtime", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "dependencies": { "ulid": "^3.0.2" @@ -9159,7 +9159,7 @@ }, "packages/opencode-plugin": { "name": "@mebular/opencode-plugin", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "engines": { "node": ">=22" @@ -9167,7 +9167,7 @@ }, "packages/service": { "name": "@mebular/service", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "engines": { "node": ">=20" @@ -9175,7 +9175,7 @@ }, "packages/skill": { "name": "@mebular/skill", - "version": "0.3.2", + "version": "0.3.4", "license": "MIT", "engines": { "node": ">=20" diff --git a/package.json b/package.json index 089c3ad5..6c40bac9 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/core", - "version": "0.3.2", + "version": "0.3.4", "description": "One shared graph for every AI assistant and device — memory and tasks, local-first, signed, auditable, direct P2P sync; MCP tools, no hosted account. | 一份记忆,每个助手,每台设备:本地优先、可审计的跨设备记忆与任务协作;提供 MCP 工具,无需托管账号。", "license": "MIT", "author": { diff --git a/packages/dsh-plugin/README.md b/packages/dsh-plugin/README.md index d3e3a4ab..e6852fca 100644 --- a/packages/dsh-plugin/README.md +++ b/packages/dsh-plugin/README.md @@ -135,7 +135,7 @@ App 与 DSH Plugin 是同一套本机 runtime 的两个入口。插件默认 `at ```bash # 安装插件(不会静默启动或下载 Mebular) -dsh plugin --profile web add @mebular/dsh-plugin@0.3.2 +dsh plugin --profile web add @mebular/dsh-plugin@0.3.4 # 开发安装 dsh plugin --profile web add ./packages/dsh-plugin @@ -179,6 +179,6 @@ DSH 通过官方 MCP client 连接同一个 daemon 的 `/mcp`;工具在 DSH
-v0.3.2 · early · MIT · © 2026 Sobert Li +v0.3.4 · early · MIT · © 2026 Sobert Li
diff --git a/packages/dsh-plugin/README_EN.md b/packages/dsh-plugin/README_EN.md index 2381d78b..28146a7f 100644 --- a/packages/dsh-plugin/README_EN.md +++ b/packages/dsh-plugin/README_EN.md @@ -135,7 +135,7 @@ An existing Mebular app or CLI attaches automatically; when no runtime exists, o ```bash # Install the plugin (it never starts or downloads Mebular silently) -dsh plugin --profile web add @mebular/dsh-plugin@0.3.2 +dsh plugin --profile web add @mebular/dsh-plugin@0.3.4 # Development install dsh plugin --profile web add ./packages/dsh-plugin @@ -179,6 +179,6 @@ DSH reaches the same daemon at `/mcp` through the official MCP client; tools app
-v0.3.2 · early · MIT · © 2026 Sobert Li +v0.3.4 · early · MIT · © 2026 Sobert Li
diff --git a/packages/dsh-plugin/package.json b/packages/dsh-plugin/package.json index f61cffb0..77e00d22 100644 --- a/packages/dsh-plugin/package.json +++ b/packages/dsh-plugin/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/dsh-plugin", - "version": "0.3.2", + "version": "0.3.4", "description": "Mebular memory, task graph, and shared Console for DeepSeek Harness. | Mebular 为 DeepSeek Harness 提供记忆、任务图与共享 Console。", "license": "MIT", "author": { diff --git a/packages/fleet/package.json b/packages/fleet/package.json index 311aa176..b01c6d92 100644 --- a/packages/fleet/package.json +++ b/packages/fleet/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/fleet", - "version": "0.3.2", + "version": "0.3.4", "description": "Cross-device multi-agent collaboration for Mebular (tasks as memory): task-as-memory dispatch and collection, no central coordinator. | Mebular 跨设备多 Agent 协作(任务=记忆):task-as-memory 的派发与回收,无中心协调。", "license": "MIT", "author": { diff --git a/packages/mcp/package.json b/packages/mcp/package.json index 8c4aef37..afb99dc2 100644 --- a/packages/mcp/package.json +++ b/packages/mcp/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/mcp", - "version": "0.3.2", + "version": "0.3.4", "description": "Mebular MCP server (stdio + Streamable HTTP): exposes Mebular memory and task capabilities to any MCP client. | Mebular MCP server(stdio + Streamable HTTP):把 Mebular 的记忆与任务能力暴露给任意 MCP client。", "license": "MIT", "author": { diff --git a/packages/mcp/src/version.mjs b/packages/mcp/src/version.mjs index 07e4239c..2158f037 100644 --- a/packages/mcp/src/version.mjs +++ b/packages/mcp/src/version.mjs @@ -5,4 +5,4 @@ // scripts/bump-version.mjs 只改这一处,scripts/verify-release-version.mjs // 校验它等于发布版本;不要在其它文件再写版本字面量。 -export const APP_VERSION = '0.3.2'; +export const APP_VERSION = '0.3.4'; diff --git a/packages/memory-runtime/package.json b/packages/memory-runtime/package.json index adbda83e..1ac4ec76 100644 --- a/packages/memory-runtime/package.json +++ b/packages/memory-runtime/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/memory-runtime", - "version": "0.3.2", + "version": "0.3.4", "description": "Mebular Memory Runtime sidecar: staging/cache/outbox, detail settling, candidate extraction, recall and model orchestration. | Mebular Memory Runtime sidecar:staging/cache/outbox、详情沉降、候选抽取、召回与模型编排。", "license": "MIT", "author": { diff --git a/packages/memory-runtime/src/sidecar/config.ts b/packages/memory-runtime/src/sidecar/config.ts index 7c1ef8dc..37b43bbf 100644 --- a/packages/memory-runtime/src/sidecar/config.ts +++ b/packages/memory-runtime/src/sidecar/config.ts @@ -14,7 +14,7 @@ import { basename, join, resolve, sep } from 'node:path'; import { readJsonFile } from './atomic-json.js'; export const SIDECAR_PACKAGE_NAME = '@mebular/memory-runtime'; -export const SIDECAR_RUNTIME_VERSION = '0.3.2'; +export const SIDECAR_RUNTIME_VERSION = '0.3.4'; export const SIDECAR_API_VERSION = 1; export const SIDECAR_CAPABILITY_API_VERSION = 1; export const SIDECAR_MIN_MCP_VERSION = '0.3.0'; diff --git a/packages/opencode-plugin/README.md b/packages/opencode-plugin/README.md index 5c444241..0cd59ad5 100644 --- a/packages/opencode-plugin/README.md +++ b/packages/opencode-plugin/README.md @@ -20,7 +20,7 @@ Mebular Memory Runtime 的 OpenCode V2 服务端插件(OpenChamber 使用) - `ctx.session.hook("context")` 可用;低于 2.2.0 或缺失时插件禁用并给出状态。 - `ctx.session.generate` 缺失时插件仍可召回/采集,但当前模型抽取标记为不可用, 不做任何伪造调用。 -- Memory Runtime HTTP 服务可用(Mebular 0.3.2)。 +- Memory Runtime HTTP 服务可用(Mebular 0.3.4)。 ## 安装 diff --git a/packages/opencode-plugin/index.js b/packages/opencode-plugin/index.js index 26060140..74e3a148 100644 --- a/packages/opencode-plugin/index.js +++ b/packages/opencode-plugin/index.js @@ -23,7 +23,7 @@ import { basename, dirname, join, resolve, sep } from 'node:path'; export const PLUGIN_ID = 'mebular.memory'; export const PACKAGE_NAME = '@mebular/opencode-plugin'; -export const PACKAGE_VERSION = '0.3.2'; +export const PACKAGE_VERSION = '0.3.4'; export const MIN_OPENCODE_VERSION = '2.2.0'; export const RUNTIME_API_PREFIX = '/memory-runtime/v1'; // 0.3 原型路径只用于拒绝旧配置,不参与任何请求构造;拆分常量避免架构守卫误判。 diff --git a/packages/opencode-plugin/package.json b/packages/opencode-plugin/package.json index 598dda37..25e97194 100644 --- a/packages/opencode-plugin/package.json +++ b/packages/opencode-plugin/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/opencode-plugin", - "version": "0.3.2", + "version": "0.3.4", "description": "Opt-in OpenCode V2 server plugin for Mebular Memory Runtime (OpenChamber). | 面向 Mebular Memory Runtime 的 OpenCode V2 可选服务端插件(OpenChamber)。", "license": "MIT", "author": { diff --git a/packages/service/package.json b/packages/service/package.json index 966bd035..117a61d9 100644 --- a/packages/service/package.json +++ b/packages/service/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/service", - "version": "0.3.2", + "version": "0.3.4", "description": "Mebular background service: platform unit generation (launchd/systemd/Task Scheduler), install/uninstall/status/logs, and process heartbeat. | Mebular 常驻组件服务化:平台单元生成(launchd/systemd/Task Scheduler)+ install/uninstall/status/logs + 进程心跳。", "license": "MIT", "author": { diff --git a/packages/skill/package.json b/packages/skill/package.json index 5a992d86..33d3a53d 100644 --- a/packages/skill/package.json +++ b/packages/skill/package.json @@ -1,6 +1,6 @@ { "name": "@mebular/skill", - "version": "0.3.2", + "version": "0.3.4", "description": "Mebular behavior layer: portable SKILL.md + MEMORY_POLICY.md and MCP client integration snippets. | Mebular 行为层:可移植的 SKILL.md + MEMORY_POLICY.md 与各 MCP client 接入片段。", "license": "MIT", "author": {