fix(contexto): tighten openclaw peerDependency range to >=2026.4.5#147
Open
Chen17-sq wants to merge 1 commit into
Open
fix(contexto): tighten openclaw peerDependency range to >=2026.4.5#147Chen17-sq wants to merge 1 commit into
Chen17-sq wants to merge 1 commit into
Conversation
`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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linked issue
Closes #140.
Summary
packages/contexto/package.jsondeclaredpeerDependencies.openclawas"*", which accepts any installed version ofopenclaw— including ones older than the API surface this plugin actually relies on. Users on an olderopenclawinstall today get no install-time warning; they hit a runtime breakage instead.The same
package.jsonalready declares a real minimum: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.yamlrecords the new specifier alongside (one-line change).Verification
Against the acceptance criteria in the issue:
peerDependencies.openclawmatchesopenclaw.compat.minGatewayVersion(>=2026.4.5)pnpm installfrom a clean checkout resolves cleanly — no other lockfile entries shiftedpnpm --filter @ekai/contexto run build(tsc --noEmit) greenThe third acceptance item — adding a CONTRIBUTING.md note that
peerDependencies.openclawandopenclaw.compat.minGatewayVersionmust 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.