Files
openclaw/docs/channels
Josh Lehman 584f6bea5b fix: migrate tlon installs to tloncorp package
Switch new Tlon installs to @tloncorp/openclaw, add an on-load config migration for existing plugins.installs.tlon npm records, and document the rollout contract for the package rename. Preserve the tlon plugin/channel id and clear stale npm resolution metadata when rewriting old install specs so future plugin updates resolve cleanly.

Regeneration-Prompt: |
  Migrate the Tlon OpenClaw plugin package from @openclaw/tlon to @tloncorp/openclaw without breaking existing installs. Keep the plugin id and channel id as tlon, switch onboarding and docs for new installs to the new npm package, and add an automatic config migration for existing plugins.installs.tlon npm records that still reference the old package. When rewriting stored install specs, clear old npm resolution metadata such as integrity and resolvedSpec so the next plugin update does not compare the new package against the old package artifact. Also capture the migration contract in repo docs so the companion tloncorp package can preserve version continuity and manifest invariants.
2026-03-11 09:12:08 -07:00
..
2026-03-01 23:40:51 -08:00
2026-03-10 23:40:10 +00:00
2026-03-10 23:40:10 +00:00
2026-03-10 23:40:10 +00:00
2026-03-08 04:49:04 +00:00