@agentchatme/openclaw 0.6.2 → 0.6.3
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/CHANGELOG.md +71 -0
- package/dist/index.cjs +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/setup-entry.cjs +1 -1
- package/dist/setup-entry.cjs.map +1 -1
- package/dist/setup-entry.js +1 -1
- package/dist/setup-entry.js.map +1 -1
- package/openclaw.plugin.json +1 -1
- package/package.json +4 -3
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,77 @@ All notable changes to `@agentchatme/openclaw` are documented here.
|
|
|
5
5
|
The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/);
|
|
6
6
|
this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## 0.6.3 — 2026-04-27
|
|
9
|
+
|
|
10
|
+
### Fix: `openclaw plugins install` failed with `EUNSUPPORTEDPROTOCOL` on ClawHub source-linked builds
|
|
11
|
+
|
|
12
|
+
0.6.2 still failed end-user installs with the same truncated `npm install
|
|
13
|
+
failed:` symptom 0.6.2 was supposed to fix. Root cause was different this
|
|
14
|
+
time and only visible after we recovered the swallowed npm log from the
|
|
15
|
+
target machine:
|
|
16
|
+
|
|
17
|
+
```
|
|
18
|
+
error code EUNSUPPORTEDPROTOCOL
|
|
19
|
+
error Unsupported URL Type "workspace:": workspace:^
|
|
20
|
+
```
|
|
21
|
+
|
|
22
|
+
The committed source `package.json` declared
|
|
23
|
+
`dependencies."@agentchatme/agentchat": "workspace:^"`. pnpm rewrites this
|
|
24
|
+
to a real semver during `pnpm pack` / `pnpm publish`, so the **npm tarball**
|
|
25
|
+
(`registry.npmjs.org/@agentchatme/openclaw/0.6.2`) is fully clean — the
|
|
26
|
+
spec resolves to `^1.3.0` there. But ClawHub builds community plugins via
|
|
27
|
+
**source-linked verification**: it zips the GitHub source tree at the
|
|
28
|
+
release tag and ships that. `pnpm pack` is never invoked on that path, so
|
|
29
|
+
the `workspace:^` spec reaches end-user machines verbatim, where OpenClaw
|
|
30
|
+
runs `npm install` (not pnpm) and npm rejects the spec at `Arborist`'s
|
|
31
|
+
ideal-tree build step.
|
|
32
|
+
|
|
33
|
+
OpenClaw's `--silent` flag (hardcoded in
|
|
34
|
+
[`src/infra/install-package-dir.ts`](https://github.com/openclaw/openclaw/blob/main/src/infra/install-package-dir.ts))
|
|
35
|
+
suppressed both stdout and stderr, so the user saw only `npm install
|
|
36
|
+
failed:` with nothing after — exactly the same surface as 0.6.1's
|
|
37
|
+
`peerDependencies` bug, but a fundamentally different root cause.
|
|
38
|
+
|
|
39
|
+
The fix is a **production-grade lockdown** — single source of truth, no
|
|
40
|
+
process gymnastics, regression-proof:
|
|
41
|
+
|
|
42
|
+
**Changed:**
|
|
43
|
+
|
|
44
|
+
- `package.json` — `dependencies."@agentchatme/agentchat"` pinned to
|
|
45
|
+
`^1.3.0` (real semver). The committed source is now installable by raw
|
|
46
|
+
npm. Bun, Yarn, npm clone, ClawHub source-linked builds — all succeed.
|
|
47
|
+
- `pnpm-workspace.yaml` (monorepo root) — added
|
|
48
|
+
`linkWorkspacePackages: true` and `preferWorkspacePackages: true`.
|
|
49
|
+
pnpm continues to symlink the in-tree SDK during development even
|
|
50
|
+
though the spec is now a normal semver range; the dev-loop is
|
|
51
|
+
unchanged. Settings live here rather than `.npmrc` because `.npmrc`
|
|
52
|
+
is `.gitignore`d project-wide to prevent npm auth-token leakage.
|
|
53
|
+
- `scripts/strip-publish-fields.mjs` — guard now rejects `workspace:` and
|
|
54
|
+
`catalog:` specs in `dependencies` in addition to `file:` and `link:`.
|
|
55
|
+
Prior comment explicitly allowed `workspace:` on the assumption that
|
|
56
|
+
pnpm pack would rewrite it; that assumption holds for the npm tarball
|
|
57
|
+
but not for ClawHub source-linked builds, so the guard is widened.
|
|
58
|
+
|
|
59
|
+
**New:**
|
|
60
|
+
|
|
61
|
+
- `scripts/verify-source-installs.mjs` — regression test wired into
|
|
62
|
+
`prepublishOnly`. Copies the source `package.json` into a fresh temp
|
|
63
|
+
dir and runs `npm install --dry-run --omit=dev --ignore-scripts ...`
|
|
64
|
+
(the same flags ClawHub-side OpenClaw uses, minus `--silent`). A
|
|
65
|
+
future commit that re-introduces a `workspace:`, `file:`, `link:`, or
|
|
66
|
+
`catalog:` spec in `dependencies` cannot reach npm or ClawHub — the
|
|
67
|
+
prepublish hook fails first with the actual npm error message.
|
|
68
|
+
|
|
69
|
+
### Upstream improvement (filed in parallel, non-blocking)
|
|
70
|
+
|
|
71
|
+
OpenClaw `src/infra/install-package-dir.ts` hardcodes `--silent` on the
|
|
72
|
+
spawned `npm install`, which suppresses every user-actionable error.
|
|
73
|
+
Combined with the failure handler that formats `"npm install failed: " +
|
|
74
|
+
(stderr || stdout).trim()`, an empty buffer renders as the bare prefix.
|
|
75
|
+
A PR proposing replacement with `--loglevel=error` (or removal of the
|
|
76
|
+
flag entirely) is filed against `openclaw/openclaw` so the next community
|
|
77
|
+
plugin author hits a real error instead of an empty one.
|
|
78
|
+
|
|
8
79
|
## 0.6.2 — 2026-04-25
|
|
9
80
|
|
|
10
81
|
### Unblock `openclaw plugins install` on stock end-user machines — strip publish-time fields
|