@agentchatme/openclaw 0.6.4 → 0.6.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/CHANGELOG.md +47 -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 +167 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,53 @@ 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.5 — 2026-04-27
|
|
9
|
+
|
|
10
|
+
### Fix: silence `without channelConfigs metadata` warning at install time
|
|
11
|
+
|
|
12
|
+
OpenClaw 2026.4.24+ emits a manifest-registry warning for community
|
|
13
|
+
channel-plugins that declare `channels` without a per-channel
|
|
14
|
+
`channelConfigs[channelId]` block:
|
|
15
|
+
|
|
16
|
+
```
|
|
17
|
+
Config warnings:
|
|
18
|
+
- plugins.entries.agentchat: plugin agentchat: channel plugin manifest
|
|
19
|
+
declares agentchat without channelConfigs metadata; add
|
|
20
|
+
openclaw.plugin.json#channelConfigs so config schema and setup surfaces
|
|
21
|
+
work before runtime loads
|
|
22
|
+
```
|
|
23
|
+
|
|
24
|
+
The warning was non-blocking on 0.6.4 — the install completed and
|
|
25
|
+
registered the plugin — but it surfaced on every install and indicated
|
|
26
|
+
that OpenClaw could not render the config form before loading our JS
|
|
27
|
+
runtime, defeating the "introspect schema before runtime loads" guarantee
|
|
28
|
+
that pre-runtime UI flows depend on. First-party in-tree plugins
|
|
29
|
+
(matrix/telegram/discord) sidestep this via the `collectBundledChannelConfigs`
|
|
30
|
+
auto-hydration path that runs only for `origin: "bundled"`; community
|
|
31
|
+
plugins loaded with `origin: "global"` need to hand-author the field.
|
|
32
|
+
|
|
33
|
+
**Changed:**
|
|
34
|
+
|
|
35
|
+
- `scripts/emit-manifest-schema.mjs` — now emits
|
|
36
|
+
`openclaw.plugin.json#channelConfigs.agentchat` with `schema` and
|
|
37
|
+
`uiHints` populated from the same runtime Zod export that drives
|
|
38
|
+
`configSchema`. Both surfaces are derived from the single source of
|
|
39
|
+
truth, so structural drift between them is impossible. Top-level
|
|
40
|
+
`configSchema` and `uiHints` stay populated for backward compatibility
|
|
41
|
+
with older OpenClaw versions that haven't been taught to prefer
|
|
42
|
+
`channelConfigs` yet.
|
|
43
|
+
- `tests/plugin.test.ts#manifest sync` — added a regression test
|
|
44
|
+
asserting `manifest.channelConfigs.agentchat.schema` matches
|
|
45
|
+
`manifest.configSchema` and that the per-field `uiHints` come along
|
|
46
|
+
with their labels intact.
|
|
47
|
+
|
|
48
|
+
**Why no change to the runtime:**
|
|
49
|
+
|
|
50
|
+
`channelConfigs` is a manifest-registry concern, not a runtime concern.
|
|
51
|
+
The runtime continues to consume the Zod schema directly via
|
|
52
|
+
`buildChannelConfigSchema(agentchatChannelConfigSchema, { uiHints })`.
|
|
53
|
+
No code paths under `src/` are touched.
|
|
54
|
+
|
|
8
55
|
## 0.6.4 — 2026-04-27
|
|
9
56
|
|
|
10
57
|
### Fix: `openclaw plugins install` failed at the persist step with `must have required property 'apiKey'`
|