Merge pull request #998 from RooCodeInc/release/v0.30.0

Promote v0.30.0 to production

Author: mrubens

.docker/app/Dockerfile

@@ -1,4 +1,8 @@
-# syntax=docker/dockerfile:1.7
+# No `# syntax=` directive on purpose: this Dockerfile only needs features the
+# BuildKit built-in frontend already provides (secret mounts, multi-stage
+# targets), and resolving an external docker/dockerfile frontend image has
+# crashed CI builders ("frontend grpc server closed unexpectedly") when the
+# cached frontend image goes bad.
 #
 # Shared application image for the Roomote control plane.
 #

.github/workflows/publish-ghcr.yml

@@ -456,31 +456,11 @@ jobs:
 
           echo "Announced GitHub Release $VERSION in Discord"
 
-  notify-ops:
-    name: Notify ops repository
-    runs-on: ubuntu-latest
-    needs: publish
-    if: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' && vars.ROOMOTE_OPS_REPO != '' }}
-    permissions:
-      contents: read
-    steps:
-      - name: Send repository dispatch
-        env:
-          GH_TOKEN: ${{ secrets.ROOMOTE_OPS_DISPATCH_TOKEN }}
-          OPS_REPO: ${{ vars.ROOMOTE_OPS_REPO }}
-        run: |
-          set -euo pipefail
-          : "${GH_TOKEN:?ROOMOTE_OPS_DISPATCH_TOKEN is required}"
-          event_type=roomote-main-build
-          image_tag="main-${GITHUB_SHA:0:8}"
-          gh api "repos/${OPS_REPO}/dispatches" \
-            -f "event_type=${event_type}" \
-            -f "client_payload[image_tag]=${image_tag}" \
-            -f "client_payload[sha]=${GITHUB_SHA}" \
-            -f "client_payload[ref]=${GITHUB_REF}"
-
-  # Keep staging Cloud delivery independent from the existing Roomote-Ops
-  # production path. This job only follows successful develop image publishes.
+  # This job only follows successful develop image publishes. (The old
+  # notify-ops job that dispatched hand-built fleet deploys to Roomote-Ops
+  # was removed 2026-08-01 with that repo's retirement: every tenant is
+  # Cloud-managed, and the dispatch had been redeploying quiesced legacy
+  # projects on every main build.)
   notify-staging-cloud:
     name: Notify staging Cloud
     runs-on: ubuntu-latest

.gitignore

@@ -77,6 +77,7 @@ AGENTS.local.md
 # .claude -> .agents symlink, which filesystem walkers follow but git does not.
 /.agents/worktrees/
 /.claude/worktrees/
+/.worktrees/
 
 # e2e
 artifacts/ci-e2e/

CHANGELOG.md

@@ -2,6 +2,33 @@
 
 This file tracks product releases for Roomote (single monorepo version). Automated release entries are prepended by `pnpm run version`.
 
+## 0.30.0 (2026-08-02)
+
+This release makes custom automations more flexible and reliable while improving task recovery and cross-channel follow-ups.
+
+### Highlights
+
+- Schedule custom automations with presets, cron, or natural language, choose a model for each automation, and manage them through Roomote.
+- Route manager summaries, suggestions, alerts, and other automation output to Discord as well as Slack.
+- Recover from model-provider errors in the same task without losing the active workspace.
+- Preserve conversational context when continuing Slack- or Discord-linked tasks from the web.
+
+### Minor changes
+
+- Let administrators choose a model for each custom automation while existing automations continue using the deployment default.
+- Let administrators use a Discord channel as the shared destination for manager summaries, suggestions, alerts, and other automation output.
+- Let administrators schedule custom automations with presets, cron, or natural language in a deployment-wide timezone, and manage their full lifecycle through Roomote's MCP tools.
+
+### Patch changes
+
+- Make app image builds more reliable by using BuildKit's built-in Dockerfile frontend instead of launching an unnecessary external frontend image.
+- Return actionable validation messages when Roomote manages custom automations, and record unexpected API failures in server logs for troubleshooting.
+- Launch due custom automations even when an earlier run remains active while retaining duplicate-launch protection.
+- Preserve conversational context when users continue Slack- or Discord-linked tasks from the web, including concurrent follow-ups and image-only replies.
+- Keep active task sandboxes available after model-provider errors so users can recover with a follow-up without losing workspace state.
+- Let users browse and configure Automations without a misleading Slack prerequisite while retaining provider-specific setup and permission guidance.
+- Use kickoff copy that matches the environment selected from Slack's manual routing picker instead of referring to a rejected suggestion.
+
 ## 0.29.0 (2026-08-01)
 
 This release expands model reasoning and preset options while improving LiteLLM routing, invite previews, and environment guidance.