release: version packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@paleo/alignfirst-developer-openclaw-plugin@0.1.0

Minor Changes

• 6d72df2: Added durable activation and claim handling for confirmed Slack and Discord thread starters.

@paleo/openclaw-channel-mock-core@0.8.0

Minor Changes

• 6d72df2: Added configurable Slack thread routing, native starter receipt shapes, and canonical thread-session delivery. A send whose target names a stored thread now lands in that thread under its parent conversation, with or without an accompanying threadId. Discord-shaped thread-create now returns the native { ok, thread } shape, with partial: true when the thread exists but its starter was not delivered; the former threadId, target and message fields are gone. Discord-shaped thread-reply now accepts a bare threadId as its delivery target, as bundled Discord does. The test-bus fault injector accepts threadOnly: true to fail only a threaded send.

Patch Changes

• 6d72df2: Matched Discord thread behavior: inbound metadata uses native channel targets, send with threadName renames the resolved thread, and thread-reply leaves its name unchanged.

@paleo/openclaw-discord-mock@0.4.0

Minor Changes

• 6d72df2: Added configurable Slack thread routing, native starter receipt shapes, and canonical thread-session delivery. A send whose target names a stored thread now lands in that thread under its parent conversation, with or without an accompanying threadId. Discord-shaped thread-create now returns the native { ok, thread } shape, with partial: true when the thread exists but its starter was not delivered; the former threadId, target and message fields are gone. Discord-shaped thread-reply now accepts a bare threadId as its delivery target, as bundled Discord does. The test-bus fault injector accepts threadOnly: true to fail only a threaded send.

Patch Changes

• Updated dependencies [6d72df2]
• Updated dependencies [6d72df2]
  • @paleo/openclaw-channel-mock-core@0.8.0

@paleo/openclaw-slack-mock@0.4.0

Minor Changes

• 6d72df2: Added configurable Slack thread routing, native starter receipt shapes, and canonical thread-session delivery. A send whose target names a stored thread now lands in that thread under its parent conversation, with or without an accompanying threadId. Discord-shaped thread-create now returns the native { ok, thread } shape, with partial: true when the thread exists but its starter was not delivered; the former threadId, target and message fields are gone. Discord-shaped thread-reply now accepts a bare threadId as its delivery target, as bundled Discord does. The test-bus fault injector accepts threadOnly: true to fail only a threaded send.

Patch Changes

• Updated dependencies [6d72df2]
• Updated dependencies [6d72df2]
  • @paleo/openclaw-channel-mock-core@0.8.0

@paleo/openclaw-test@0.17.0

Minor Changes

• 6d72df2: Added ctx.busUrl to ScenarioContext for direct test-bus calls.

Patch Changes

• 6d72df2: Fixed the pnpm fixture-install example for current pnpm releases.
• Updated dependencies [6d72df2]
• Updated dependencies [6d72df2]
  • @paleo/openclaw-channel-mock-core@0.8.0
  • @paleo/openclaw-slack-mock@0.4.0
  • @paleo/openclaw-discord-mock@0.4.0

@paleo/alcode@0.13.1

Patch Changes

• 6d72df2: Prevented OpenClaw completion wake-ups from being lost by keeping the wake command's semicolon on the alcode command line.

alignfirst@0.1.1

Patch Changes

• 6d72df2: Tightened merge conflict resolution and validation guidance.