cloud: v0.36.0

0.36.0 (2026-10-09)

Features

• ui: add swipe, long-press and double-tap gestures (#786) (6f72eae)

Bug Fixes

• cloud: document the Postgres outbox and public HTTPS fetch, and end an outbox batch with its claim (#787) (d613448)
• scripts: run one heavy check or test run per machine with bounded type checkers (#791) (bbc4932)
• ui: keep phone keyboards from capitalizing user names and addresses (#792) (5b9b9a1)
• ui: keep short table columns readable next to long ones (#785) (4f12a78)
• ui: keep the chat composer's formatting row short and aligned with the field (#789) (ae018fc)

Operator notes

TL;DR: A small follow-up to 0.35.0, released quickly for one fix: tables with a short column next to a long one, for example a glossary in a Notebooks Book, broke every word of the short column letter by letter (#785). There is nothing to configure. There are no new environment variables and no Compose changes, the release has the same 27 images, and the JetStream reservation does not change. Core adds one table and builds two search indexes on the outgoing-mail send log in the background (#794). You can roll back to 0.35.0, but the table bug returns. #793, #794 and #790 are in the tag but missing from the changelog above (see "Also in this release"). If you skipped 0.35.0, its security notes still apply: update the gateway first (see cloud-v0.35.0).

Reference pages at this tag: Let an app read other apps' mail, Outgoing mail upgrade and rollback, Deliver an outbox.

What changes

• Tables are readable again (#785). Whole words now set a column's minimum width; only a word too long for the table still wraps. This covers the Notebooks Book, Markdown tables in every application and MarkdownView. Each application carries the fix in its own image.
• The live-update outbox stops at the end of its claim (#787). A batch starts no further publish once its claim has expired. Before, a slow batch could keep publishing while another replica had already claimed the same rows, so later updates could overtake earlier ones. Delivery stays at least once. Replicas of 0.35.0 and 0.36.0 share the same claim lock, so a rolling update is safe, and the fix is complete once every replica runs 0.36.0. Outgoing HTTPS requests from Assistant Studio apps now also refuse the IPv6 documentation range 3fff::/20.
• Gestures in @k2b/ui (#786). The new GestureMenu adds swipe, long press and double tap on phones, each backed by a visible menu entry. It is additive, and no built-in application uses it yet.
• Smaller UI fixes: phone keyboards no longer capitalize or autocorrect user name, email, URL and password fields (#792). The chat composer's formatting row offers only Bold, Italic and Bullet list, the attach button shows a plus, and Ctrl/Cmd+E and Ctrl/Cmd+Shift+X go back to the browser (#789).

Deploy order

Update in any order; there is no schema change outside Core. Two points:

• Core creates outgoing_mail.app_log_access during setup, then builds two GIN search indexes on the send log in the background, one of them with pg_trgm, which Core already requires. Core starts and sends mail while they build. On a large log, the build takes about a minute per million records on a single core, and until it finishes a send-log search can stop after five seconds with bad_input. A build that fails or is interrupted logs a warning from core:outgoing-mail and runs again on the next start of Core.
• Applications that use the new mail features of @k2b/cloud 0.29.1 (#794): no built-in application does. Deploy such an application only after the rest of Cloud runs 0.36.0. Searches with q or recipient need database functions that Core 0.36.0 creates. A 0.35.0 gateway rejects the registry entry of an application that declares mail:read and does not route it. To grant send-log access with the CLI, run cld plugins update admin first.

Rollback

• Rolling back to 0.35.0 is safe, and the table bug returns.
• First stop or roll back any application that declares mail:read, because 0.35.0 services, the gateway included, reject its registry entry.
• Core keeps the grant table and the search indexes, and 0.35.0 ignores them. The grants take effect again after the next update.
• Do not roll back the gateway below 0.35.0 (see the 0.35.0 security notes).

Also in this release

These commits are in the tag but missing from the changelog above. #793 and #794 merged while the release PR was queued:

• #793 fix(ai): make the work line open reliably, one level deep, and show approvals the calm way. The Assistant's work line opens on every click, Enter or Space. Steps sit one level deep. A decided approval turns into a one-line receipt. An approval still waiting when a turn ends is now stored as expired, and older versions ignore that value. The fix ships in @k2b/cloud 0.29.1 and @k2b/ui 0.20.0.
• #794 feat(cloud): let an app search the send log of the apps it works with. Under Administration → Outgoing mail → Apps, or with cld admin outgoing-mail apps set-log-access, you can let an application that declares mail:read read the send log of other applications. Nothing is shared until you grant it, and Core's mail can never be granted. The reader sees recipients, subjects, delivery errors, senders and attachment names, but no message text, and decides itself which of its users see them. Grants follow application IDs: when you remove an application for good, clear its grants (--own-only) and remove it from other applications' selections, otherwise an application registered later under the same ID inherits them. This feature ships in the patch release @k2b/cloud 0.29.1, because release-please could no longer version the queued release PR.
• #790 build(ssr), hidden by release-please as a build commit. @k2b/ssr is now developed in this repository, and the images build it from source. This release publishes no new @k2b/ssr, and @k2b/cloud 0.29.1 still pins @k2b/ssr 0.15.0. Its only runtime change in the images is a linear-time normalizeBasePath, which CodeQL had flagged. No action is needed.