Skip to content

chore(release): v0.3.29 - #133

Merged
sulthannauval merged 1 commit into
mainfrom
release/v0.3.29
Sep 26, 2026
Merged

sulthannauval merged 1 commit into
mainfrom
release/v0.3.29

Conversation

@sulthannauval

Copy link
Copy Markdown
Member

Console release paired with RantaiClaw v0.32.0-alpha. Step one of the two-repo sequence: the console ships first, because RantaiClaw pins its tag.

What this is

package.json 0.3.28 → 0.3.29, and a [0.3.29] section in CHANGELOG.md. scripts/check-version.mjs checks "not behind", so bumping before the tag exists passes:

package.json 0.3.29 is not behind the newest tag v0.3.28.

Changelog edits beyond moving [Unreleased]

  • A pairing note opens the section. Three entries read fields that only RantaiClaw v0.32.0-alpha serves: the Slack and Discord checklist (setup_checklist, absent from v0.31.0-alpha), the Lark card (RantaiClaw #822/#825) and the WhatsApp Web restart wait (restarts_runtime, RantaiClaw #820). Each entry already says how it degrades on an older gateway.
  • The feat(channels): slack and discord cards show the platform-side setup checklist #132 entry said "the catalog now carries" setup_checklist. The console does not produce the catalog. The field arrives with RantaiClaw v0.32.0-alpha, and the entry now says so.
  • The fix(channels): slack caveat comment matches the gateway's new wording #131 entry is dropped. It changed a code comment and a test fixture, and nothing an operator sees came from it. The wording it relays ships in RantaiClaw's changelog (#876).

Checks

node scripts/check-version.mjs --self-test and the check itself pass · npx tsc --noEmit clean · npm run lint 0 errors, 39 warnings (no code touched) · npm test 768 passed · npm run build clean.

Non-goals

No code changes, two files. The optional channels-panel.tsx:751 formatting chore is left out.

- package.json 0.3.28 -> 0.3.29 and a [0.3.29] section in CHANGELOG.md, paired with RantaiClaw v0.32.0-alpha
- the section opens with a pairing note: the Slack and Discord checklist (setup_checklist), the Lark card and the WhatsApp Web restart wait (restarts_runtime) read fields only that runtime serves, and each entry already says how it degrades on an older gateway
- the checklist entry now says the field comes from RantaiClaw v0.32.0-alpha's /api/v1/channels instead of "the catalog now carries" it
- the Slack caveat entry is dropped: that PR changed a code comment and a test fixture, nothing an operator sees
@sulthannauval
sulthannauval merged commit 06bd7a4 into main Sep 26, 2026
2 checks passed
@sulthannauval
sulthannauval deleted the release/v0.3.29 branch September 26, 2026 06:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant