Skip to content

chore(release): v0.3.29 #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sulthannauval merged 1 commit into from
Sep 26, 2026
Merged

chore(release): v0.3.29 #133

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,14 +10,21 @@ carries the paired entry and the release notes.

## [Unreleased]

## [0.3.29] — 2026-09-26

Paired with RantaiClaw `v0.32.0-alpha`. Three entries below read what only that
runtime serves: the Slack and Discord checklist (`setup_checklist`), the Lark card
(a catalog that recognises Lark) and the WhatsApp Web restart wait
(`restarts_runtime`). Against an older gateway each one degrades as its entry says.

### Added

- **Slack and Discord setup cards show the platform-side checklist the gateway sends.**
A connected Slack or Discord bot can still be deaf to DMs or receive empty messages when the
platform side is misconfigured, and the console used to show nothing about that. The catalog now
carries an optional `setup_checklist` on the `slack` and `discord` rows; the cards render it
verbatim in the connect state, above the token input, under a short "On the platform side"
heading. A gateway that does not yet send the field renders nothing extra — no fallback copy,
platform side is misconfigured, and the console used to show nothing about that. From RantaiClaw
`v0.32.0-alpha`, `/api/v1/channels` carries an optional `setup_checklist` on the `slack` and
`discord` rows, and the cards render it verbatim in the connect state, above the token input,
under a short "On the platform side" heading. A gateway that does not yet send the field renders nothing extra — no fallback copy,
no heading. The other channels (Telegram, WhatsApp Web, Lark) never get a checklist, and a
buggy catalog row that carries one on the wrong key is ignored by the render, which is gated
by the card's own key.
Expand Down Expand Up @@ -56,10 +63,6 @@ carries the paired entry and the release notes.
Lark `open_id` (`ou_…`); pasting a Lark `user_id` into the old label built an allowlist that never
matched. The field is now labelled "Allowed Lark open_ids (ou_…, comma-separated)" with a short
hint that `/claim` adds one automatically. (#130)
- **The Slack card's caveat comment matches the gateway's new wording.** With Socket Mode on and
a `channel_id` set, the bot now ignores every other channel while direct messages still arrive;
the comment on `SlackCard` and the Socket Mode test fixture both relay that sentence, and two
stale "three cards" comments are reworded to drop the count.

## [0.3.28] — 2026-09-08

Expand Down
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "rantaiclaw-ui",
"version": "0.3.28",
"version": "0.3.29",
"private": true,
"description": "Standalone web UI for the RantaiClaw agent runtime (chat + ops dashboard).",
"scripts": {
Expand Down
Loading