Skip to content

fix(contexto): tighten openclaw peerDependency range to >=2026.4.5#147

Open
Chen17-sq wants to merge 1 commit into
ekailabs:mainfrom
Chen17-sq:fix/140-tighten-openclaw-peerdep
Open

fix(contexto): tighten openclaw peerDependency range to >=2026.4.5#147
Chen17-sq wants to merge 1 commit into
ekailabs:mainfrom
Chen17-sq:fix/140-tighten-openclaw-peerdep

Conversation

@Chen17-sq
Copy link
Copy Markdown

Linked issue

Closes #140.

Summary

packages/contexto/package.json declared peerDependencies.openclaw as "*", which accepts any installed version of openclaw — including ones older than the API surface this plugin actually relies on. Users on an older openclaw install today get no install-time warning; they hit a runtime breakage instead.

The same package.json already declares a real minimum:

"openclaw": {
  "compat": {
    "pluginApi": ">=2026.4.5",
    "minGatewayVersion": "2026.4.5"
  }
}

This PR aligns the peer range to that minimum so pnpm install (or any other package manager that surfaces peer-range warnings) tells the user to upgrade before they trip the runtime error.

Change

   "peerDependencies": {
-    "openclaw": "*"
+    "openclaw": ">=2026.4.5"
   },

pnpm-lock.yaml records the new specifier alongside (one-line change).

Verification

Against the acceptance criteria in the issue:

  • peerDependencies.openclaw matches openclaw.compat.minGatewayVersion (>=2026.4.5)
  • pnpm install from a clean checkout resolves cleanly — no other lockfile entries shifted
  • No other workspace package depends on the wildcard:
    $ grep -rn '"openclaw"' packages/ --include=package.json
    packages/contexto/package.json:16:    "openclaw",
    packages/contexto/package.json:38:    "openclaw": ">=2026.4.5"
    packages/contexto/package.json:44:  "openclaw": {
    
  • pnpm --filter @ekai/contexto run build (tsc --noEmit) green

The third acceptance item — adding a CONTRIBUTING.md note that peerDependencies.openclaw and openclaw.compat.minGatewayVersion must move together on future bumps — is intentionally NOT in this PR. Happy to follow up if you'd like that addition; left out to keep this PR scoped to the one-line behavioural fix.

`peerDependencies.openclaw` was declared as `*`, which accepts any
version including ones older than the API surface this plugin
actually relies on. Users on an older `openclaw` install today get
no install-time warning — they hit a runtime breakage instead.

The same `package.json` already pins a real minimum via
`openclaw.compat.minGatewayVersion = "2026.4.5"`; align the peerDep
to match so `pnpm install` (or any package manager that surfaces
peer-range warnings) tells the user to upgrade BEFORE they trip the
runtime error.

Closes ekailabs#140.

Test plan
---------
- `pnpm install` resolves cleanly (lockfile updated to record the
  new specifier; no other package's resolution changed).
- `pnpm --filter @ekai/contexto run build` (tsc --noEmit) is green.
- No other workspace package depends on the wildcard — verified with
  `grep -rn '"openclaw"' packages/ --include=package.json` (only
  `packages/contexto/package.json` references it).

Acceptance criteria from the issue:
- [x] `peerDependencies.openclaw` matches `openclaw.compat.minGatewayVersion`
- [x] `pnpm install` from a clean checkout resolves cleanly
- [ ] CONTRIBUTING.md note about keeping the two fields in lockstep —
      happy to add in a follow-up if maintainer wants it; keeping this
      PR scoped to the one-line behavioral fix.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[contexto]: Tighten openclaw peerDependency version range

1 participant