Skip to content

v2.4.0

Latest
Latest

Choose a tag to compare

View all tags
@ekinnee ekinnee released this 22 Oct 16:00
v2.4.0
9eb2cf0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

OmniRoute OpenClaw v2.4.0

Minor release for @ekinnee/omniroute-provider.

Added

  • Web search honors the existing tools.web.search.maxResults setting when a
    call omits count, and displays the effective default in its parameter
    description. Explicit-count handling is unchanged; without a configured
    default, omitted counts still request 5 results. Requested by
    sprintberlin, implemented in
    PR #90.

Fixed

  • Image, video, music, and speech providers use async readiness checks when the
    public OpenClaw SDK supplies them, avoiding legacy SDK calls and the speech
    readiness deprecation warning on the newer host path.
  • Standalone catalog auditing prepares cold runtime configuration through the
    async SDK reader when available. Older supported hosts retain their existing
    synchronous behavior; rejected async calls are never retried synchronously.
    Both changes are in
    PR #89.

Compatibility and upgrade behavior

  • Minimum OpenClaw version remains 2026.7.1; peer and plugin API ranges remain
    >=2026.7.1-0. No new plugin configuration or credential migration is required.
  • Existing tools.web.search.maxResults values now take effect for calls that
    omit count. Existing explicit counts keep their previous handling.
  • SDK contracts that are unavailable on older hosts are detected through public
    exports. The release does not require a beta or development host.
  • Direct callers of deprecated synchronous host APIs can still produce their
    own warnings. The plugin's async readiness path avoids those legacy calls.

Verification scope

The merged feature changes have passing hosted unit and packed compatibility
checks. Adapter evidence covers async credential readiness, cold standalone
config loading and default/named-agent selection, and search-count requests
through the real SDK guarded transport against a synthetic local service.
These checks do not establish deployed Gateway, model, or media-generation
behavior. Release publication and public installation are verified separately.

ClawHub inspection note

ClawHub's static inspector reports deprecation warnings for the two legacy SDK
fallback references retained for supported older hosts. Hosts exposing the async
APIs use the new paths; the packed compatibility tests cover that selection.
The static warnings are not a claim that those newer paths call the retired
APIs. Eventual removal of the older-host paths remains tracked in
issue #88.

Publication verification

  • Published on GitHub and ClawHub from commit
    9eb2cf01c74a12283eb48dba8f63e873f567072e.
  • Hosted unit tests passed all 181 cases; floor/current/beta compatibility checks
    passed. The release publisher completed successfully.
  • ClawHub reports version 2.4.0 as published/latest with a clean scan and
    source linkage to refs/tags/v2.4.0.
  • The downloaded public artifact matches the exact release-workflow artifact:
    SHA-256 f603158e95259a238f3706b8f27711eb7b32bb3e2e0565d8a84f456f4f3ad3fd.
  • A normal version-pinned public installation in disposable OpenClaw state
    succeeded. Nine capability contracts, credential readiness, cold config, and
    real guarded HTTP search requests were verified on OpenClaw 2026.10.6.
    This does not claim a production Gateway upgrade or model/media generation.
Assets 2
Loading