@agentchatme/openclaw 0.7.3 → 0.7.5

package/CHANGELOG.md

@@ -7,6 +7,17 @@ this package adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.htm
 
 This package is in pre-1.0 development.
 
+## 0.7.5 — 2026-05-08
+
+- Silent + conditional `prepare` hook. 0.7.4 introduced `"prepare": "npm run build"` so ClawHub's source-linked clone could compile `dist/` after `npm install`. ClawHub also runs `npm pack --json` to build its archive artifact, and during pack npm fires our prepare lifecycle while capturing stdout to emit as a single JSON document. The build chain's human-readable logs (`tsup`, `fix-cjs-extensions`, `emit-manifest-schema`) interleaved into that captured stream and ClawHub's parser failed with `npm pack did not return JSON output` — npm published cleanly, ClawHub publish step exited 1 (workflow run 25581801153). Replaced the inline command with `scripts/prepare.mjs`, which (1) skips the build entirely when `dist/index.js` already exists (typical in CI after explicit build, and in publish flows after `prepublishOnly`), and (2) when it does build, runs with `stdio: ['inherit', 'ignore', 'inherit']` so stdout is dropped while stderr is preserved — silent success, loud failure. End-user behavior unchanged on either npm or ClawHub install.
+
+## 0.7.4 — 2026-05-08
+
+- ClawHub publishability fixes — pure metadata/build-script changes, no runtime behavior change. Two issues caused by the manifest pointing at compiled `./dist/*.js` paths while `dist/` is gitignored, so ClawHub's source-linked clone of the GitHub repo couldn't find the files the manifest promised.
+  - Added a `prepare` script (`npm run build`) so ClawHub's source-linked install builds `dist/` after `npm install`. End-user installs from the npm tarball are unaffected because `prepare` only fires on git/source installs; the published tarball already ships pre-built `dist/`.
+  - Added `env: { allOf: ["AGENTCHAT_API_KEY"] }` to `package.json#openclaw.channel.configuredState`. Mirrors the canonical OpenClaw plugin-SDK shape used by `@openclaw/discord` and other first-party channel plugins. Existing `requires.env` and `channelEnvVars` declarations are kept for backward-compatible readers.
+- Closes the ClawHub review concerns flagged on 0.7.3 — "no install spec / no code files / submitted artifact contains no runtime code." Source-link consumers now see a self-bootstrapping artifact.
+
 ## 0.7.3 — 2026-05-08
 
 - README + npm package description retitled to drop the "OpenClaw channel" framing. The audience on ClawHub is already inside OpenClaw — leading with "AgentChat for OpenClaw" or "the official OpenClaw channel plugin" reads as a category label they don't recognize. The H1 is now plain `# AgentChat`, the npm description starts `AgentChat — give your agent its own chat network…`, and the surrounding prose names AgentChat as the product instead of restating its plugin classification. Functional behavior, manifest type (`channels: ["agentchat"]`), and CLI install command are unchanged — this is a documentation rewrite, not a structural change.

package/dist/index.cjs

@@ -1862,7 +1862,7 @@ var CircuitBreaker = class {
 };
 
 // src/version.ts
-var PACKAGE_VERSION = "0.7.3";
+var PACKAGE_VERSION = "0.7.5";
 
 // src/outbound.ts
 var DEFAULT_RETRY_POLICY = {