Please publish stable release with stringEnum fix (currently only in 1.1.0-beta)

[marzliak]

Context

The current stable release (1.0.32) imports stringEnum from openclaw/plugin-sdk:

import { stringEnum } from "openclaw/plugin-sdk";

This breaks at runtime with openclaw 2026.4.14 because plugin-sdk/index.js does not re-export stringEnum:

TypeError: (0 , _pluginSdk.stringEnum) is not a function

What's already fixed

The fix is already in master (1.1.0-beta.10) — stringEnum is now defined locally instead of imported from the SDK.

Request

Could you publish a new stable release (1.1.0 or a 1.0.33 patch) so users on the stable channel get the fix without having to install a beta?

Related

Also reported the root cause to the openclaw team: openclaw/openclaw#68279

[AliceLJY]

Thanks for flagging this. The stable-release request is reasonable, especially since the runtime break is already fixed in the beta line and stable users currently hit it without an obvious workaround.

The release vehicle itself (1.1.0 vs 1.0.33) is a maintainer decision, but this issue is valid and worth tracking until the fix reaches a stable channel.