PR #51520: fix(plugins): use VERSION from version.ts in createPluginRuntime

• Repository: openclaw/openclaw
• Author: zhuowater
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/51520

Description (problem / solution / changelog)

Problem

api.runtime.version always returns "unknown" for plugins in npm-installed OpenClaw (fixes #51494).

The root cause is the local resolveVersion() function in src/plugins/runtime/index.ts, which uses a hardcoded relative path:

const pkg = require("../../../package.json") as { version?: string };

This path is based on the source directory depth (src/plugins/runtime/ → 3 levels up = repo root). After bundling, all chunks are flattened into dist/, so the path overshoots the package boundary entirely and the require call throws, causing the catch block to return "unknown".

Fix

Remove the local resolveVersion() helper and import the already-resolved VERSION constant from src/version.ts directly:

import { VERSION } from "../../version.js";
// ...
version: VERSION,

src/version.ts already solved this exact problem via a candidate-list strategy with package name validation (requirePackageName: true), and also handles bundled/embedded builds via the __OPENCLAW_VERSION__ define or OPENCLAW_BUNDLED_VERSION env var. Using it as the single source of truth eliminates the redundant, broken path resolution in the plugin runtime.

Changes

• Remove import { createRequire } from "node:module" (no longer needed)
• Remove cachedVersion module-level variable
• Remove resolveVersion() function
• Add import { VERSION } from "../../version.js"
• Replace version: resolveVersion() with version: VERSION

Testing

After this change, api.runtime.version in the plugin runtime will return the same value as openclaw --version, consistent across source, npm-installed, and bundled environments.

Changed files

• src/plugins/runtime/index.ts (modified, +3/-20)

PR #51529: fix(plugins/runtime): fix api.runtime.version in bundled and npm installs

• Repository: openclaw/openclaw
• Author: sparkyrider
• State: closed | merged: False
• Link: https://github.com/openclaw/openclaw/pull/51529

Description (problem / solution / changelog)

TL;DR

api.runtime.version was broken for bundled/npm installs because plugin runtime used a source-tree-relative package.json path. This PR switches it to the shared version resolver, keeps the "unknown" fallback behavior, and adds regression coverage.

Summary

• Problem: api.runtime.version returned "unknown" for plugins in npm-installed/bundled OpenClaw because the plugin runtime resolved ../../../package.json relative to a bundled root chunk.
• Why it matters: plugins that gate behavior on the host OpenClaw version could not reliably detect compatibility and had to special-case "unknown".
• What changed: the plugin runtime now uses the shared VERSION resolver from src/version.ts, and regression tests cover both the shared dist/*.js chunk layout and plugin-runtime alignment.
• What did NOT change (scope boundary): no gateway routing, auth, persistence, channel delivery, or plugin loader behavior changed.

Change Type (select all)

• Bug fix
• Feature
• Refactor required for the fix
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

• Closes #51494
• Related #None

User-visible / Behavior Changes

Plugins that read api.runtime.version now receive the actual OpenClaw version in npm-installed/bundled environments instead of "unknown".

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No

Repro + Verification

Environment

• OS: macOS host
• Runtime/container: Node 22 / pnpm
• Model/provider: N/A
• Integration/channel (if any): plugin runtime
• Relevant config (redacted): N/A

Steps

1. Build or inspect the bundled OpenClaw runtime where plugin runtime code is emitted into a root dist/*.js chunk.
2. Read api.runtime.version from createPluginRuntime().
3. Observe the old runtime resolves ../../../package.json from the bundled chunk and returns "unknown".

Expected

• api.runtime.version matches the installed OpenClaw version.

Actual

• api.runtime.version returned "unknown" before this fix.

Evidence

• Failing test/log before + passing after
• Trace/log snippets
• Screenshot/recording
• Perf numbers (if relevant)

Human Verification (required)

• Verified scenarios: reproduced the old bundled-path failure mode; ran targeted regression tests; built the repo; imported dist/plugins/runtime/index.js and confirmed the built artifact returns the real package version.
• Edge cases checked: shared dist/chunk.js root-chunk layout; plugin runtime fallback still normalizes unusable versions to "unknown".
• What you did not verify: third-party plugin end-to-end behavior in a separate npm-global install.

Review Conversations

• I replied to or resolved every bot review conversation I addressed in this PR.
• I left unresolved only the conversations that still need reviewer or maintainer judgment.

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: revert this PR.
• Files/config to restore: src/plugins/runtime/index.ts
• Known bad symptoms reviewers should watch for: plugins reporting "unknown" again for api.runtime.version in bundled/npm installs.

Risks and Mitigations

• Risk: plugin runtime version now depends on the shared resolver path.
• Mitigation: added regression coverage for both the shared root-chunk bundle layout and the plugin runtime contract.

Changed files

• CHANGELOG.md (modified, +1/-0)
• src/plugins/runtime/index.test.ts (modified, +6/-0)
• src/plugins/runtime/index.ts (modified, +4/-10)
• src/version.test.ts (modified, +9/-0)

PR #25: fix: migrate to plugin-sdk subpath imports for OpenClaw 2026.3.24+

• Repository: stepandel/openclaw-linear
• Author: ChrisMOxon
• State: closed | merged: True
• Link: https://github.com/stepandel/openclaw-linear/pull/25

Description (problem / solution / changelog)

Summary

• Migrate all src/ imports from the monolithic openclaw/plugin-sdk entrypoint to the new subpath exports introduced in OpenClaw 2026.3.24+
• stringEnum, optionalStringEnum, jsonResult now import from openclaw/plugin-sdk/agent-runtime
• formatErrorMessage now imports from openclaw/plugin-sdk/error-runtime
• safeParseJson now imports from openclaw/plugin-sdk/text-runtime

Fixes #24

Test plan

• Verify the plugin builds successfully with npm run build
• Confirm all tool handlers still function correctly against a Linear workspace
• Validate webhook handling and work queue processing remain operational

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Reorganized internal module dependencies to improve code maintainability and separation of concerns across the plugin.

Changed files

• src/index.ts (modified, +1/-1)
• src/tools/linear-comment-tool.ts (modified, +2/-1)
• src/tools/linear-issue-tool.ts (modified, +2/-1)
• src/tools/linear-project-tool.ts (modified, +2/-1)
• src/tools/linear-relation-tool.ts (modified, +2/-1)
• src/tools/linear-team-tool.ts (modified, +2/-1)
• src/tools/queue-tool.ts (modified, +1/-1)
• src/webhook-handler.ts (modified, +1/-1)
• src/work-queue.ts (modified, +1/-1)