Lockstep release with @latitude-data/openclaw-telemetry 0.0.8, which drops the apiKey / project required constraint from the plugin's configSchema. RUNTIME_VERSION is bumped to 0.0.8 so latitude-openclaw install pins to the fixed runtime.
Fixed
- Install, upgrade, and re-keying no longer fail on OpenClaw 2026.5+.
openclaw plugins install <spec> --force(this CLI's step 2) recreatesplugins.entries[id]with an emptyconfigand validates it against the plugin'sconfigSchemabefore the CLI layers credentials in (step 3). Newer OpenClaw enforcesconfigSchema.requiredat that point, so the transient configless entry aborted the install withinvalid config: must have required property 'apiKey'— including when re-running to replace an existing entry's API key. The fix is in the runtime manifest (requiredremoved); this CLI bumpsRUNTIME_VERSIONto0.0.8to install it. No CLI code change beyond the pin. - Installer links now point to the current Latitude docs and API key settings URLs.