Repository navigation
Tags
Tags
chore: release main (#1731) 🤖 I have created a release *beep* *boop* --- <details><summary>app-runtime: 0.11.1</summary> ## [0.11.1](app-runtime-v0.11.0...app-runtime-v0.11.1) (2026-11-05) ### Features * stop streaming replies to external platforms ([#1729](#1729)) ([ddc8d64](ddc8d64)) </details> <details><summary>node: 0.1.8</summary> ## [0.1.8](node-v0.1.7...node-v0.1.8) (2026-11-05) ### Features * **core:** authenticate to Rome Cloud with signer JWTs ([#1718](#1718)) ([bd455bf](bd455bf)) ### Dependencies * The following workspace dependencies were updated * dependencies * @rome-os/node-core bumped to 0.1.7 </details> <details><summary>node-core: 0.1.7</summary> ## [0.1.7](node-core-v0.1.6...node-core-v0.1.7) (2026-11-05) ### Features * **core:** authenticate to Rome Cloud with signer JWTs ([#1718](#1718)) ([bd455bf](bd455bf)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release main (#1731) 🤖 I have created a release *beep* *boop* --- <details><summary>app-runtime: 0.11.1</summary> ## [0.11.1](app-runtime-v0.11.0...app-runtime-v0.11.1) (2026-11-05) ### Features * stop streaming replies to external platforms ([#1729](#1729)) ([ddc8d64](ddc8d64)) </details> <details><summary>node: 0.1.8</summary> ## [0.1.8](node-v0.1.7...node-v0.1.8) (2026-11-05) ### Features * **core:** authenticate to Rome Cloud with signer JWTs ([#1718](#1718)) ([bd455bf](bd455bf)) ### Dependencies * The following workspace dependencies were updated * dependencies * @rome-os/node-core bumped to 0.1.7 </details> <details><summary&g 10BC8 t;node-core: 0.1.7</summary> ## [0.1.7](node-core-v0.1.6...node-core-v0.1.7) (2026-11-05) ### Features * **core:** authenticate to Rome Cloud with signer JWTs ([#1718](#1718)) ([bd455bf](bd455bf)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
fix(web): mark connected services that need attention (#1720) ## What this PR does With Available as the default, a connection that needs attention is hidden behind Connected. The count alone does not show that something needs fixing. This follows #1717 and addresses its review finding about attention being hidden behind the Connected tab. Add a small attention dot after the Connected count, using the same size and color as the row status dot. ## Design & Invariants - Broken connections, unknown accounts, runtime degradation, and Composio connections that need attention show the dot. - The dot reflects all connected services, not search results. Searching or viewing Connected does not clear it. Resolving the underlying problem clears it. - Counts, the default tab, manual selections, search navigation, and row order stay unchanged. - The dot is hidden from assistive technology. Visually hidden text adds “needs attention” to the Connected radio name, translated in English and Simplified Chinese. - At widths up to 360px, smaller tab insets keep both controls visible with four-digit counts. Other controls keep their existing spacing. ## Test plan - [x] Healthy connections: no dot or accessible warning appears. Available stays selected by default. - [x] Broken, unknown-account, and degraded connections: the Connected label shows one dot after the count, with the accessible warning. - [x] A Composio connection needs attention: the dot appears after its asynchronous response, including when search hides that row. - [x] Search hides a broken connection, then Connected is selected: the dot remains. Counts and search navigation retain their behavior. - [x] Refresh a broken connection as healthy: the dot and accessible warning disappear without changing the selected tab. - [x] Inspect healthy and attention states at 1280×900, touch-enabled 390×844, and touch-enabled 320×800: both controls remain visible without horizontal page scrolling. - [x] Inspect selected and unselected states in light and dark mode: the tab dot matches the row dot at 8×8px. Four-digit counts fit at 320px. - [ ] Exercise real provider health recovery and full-stack startup. These checks use mock responses, not a running backend. Exercised with fake-backed component tests, translation-key checks, and isolated Chromium sessions against the static mock build. Six new attention-positive cases fail without the implementation. The healthy negative case passes with or without it. ### Screenshots All screenshots use synthetic response fixtures. | Default Available state, light mode | Desktop 1280×900 | Phone 390×844, touch on | Narrow 320×800, touch on | |---|---|---|---| | Healthy, no dot |  |  |  | | Needs attention, dot shown |  |  |  | Connected selected, with matching tab and row dots:  Dark mode, Connected selected:  ## Not in this PR - Theme palette changes. The existing light warning color has 1.69–1.83:1 contrast against the tab backgrounds, below 3:1, and is reused unchanged. - Sidebar indicators, banners, notifications, tooltips, or new automatic navigation. This indicator is limited to the Connected label. 🤖 Generated with [Rome OS](https://github.com/rome-os/rome) Co-authored-by: Rome OS <noreply@romeos.cc>
chore: release main (#1731) 🤖 I have created a release *beep* *boop* --- <details><summary>app-runtime: 0.11.1</summary> ## [0.11.1](app-runtime-v0.11.0...app-runtime-v0.11.1) (2026-11-05) ### Features * stop streaming replies to external platforms ([#1729](#1729)) ([ddc8d64](ddc8d64)) </details> <details><summary>node: 0.1.8</summary> ## [0.1.8](node-v0.1.7...node-v0.1.8) (2026-11-05) ### Features * **core:** authenticate to Rome Cloud with signer JWTs ([#1718](#1718)) ([bd455bf](bd455bf)) ### Dependencies * The following workspace dependencies were updated * dependencies * @rome-os/node-core bumped to 0.1.7 </details> <details><summary>node-core: 0.1.7</summary> ## [0.1.7](node-core-v0.1.6...node-core-v0.1.7) (2026-11-05) ### Features * **core:** authenticate to Rome Cloud with signer JWTs ([#1718](#1718)) ([bd455bf](bd455bf)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
chore: release main (#1654) 🤖 I have created a release *beep* *boop* --- <details><summary>app-runtime: 0.11.0</summary> ## [0.11.0](app-runtime-v0.10.0...app-runtime-v0.11.0) (2026-11-05) ### ⚠ BREAKING CHANGES * **app-runtime:** Sent.message is optional. * **app-runtime:** remove recordOutboundMessage; apps send through the host's chats ([#1677](#1677)) ### Features * **app-runtime:** leave Sent.message out when Rome cannot read the send back ([#1690](#1690)) ([6576d1e](6576d1e)) * **app-runtime:** name a send refusal SendRefused ([0ca19c0](0ca19c0)) * **app-runtime:** refuse a reply where the platform cannot quote, and quote natively on Discord ([#1680](#1680)) ([167a416](167a416)) * **app-runtime:** remove recordOutboundMessage; apps send through the host's chats ([#1677](#1677)) ([15fe07d](15fe07d)) * **connections:** send an approval card as its plain text where it cannot be drawn ([#1682](#1682)) ([523d9b0](523d9b0)) ### Bug Fixes * **app-runtime:** refuse a send whose attachment the platform cannot carry, as attachment_unsupported, before anything goes out ([0ca19c0](0ca19c0)) * **app-runtime:** send `text` in place of the text parts on every platform when it says anything ([0ca19c0](0ca19c0)) * **web:** distinguish automated chat messages ([#1620](#1620)) ([cd6d139](cd6d139)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
PreviousNext