Promote v0.30.1 to production

[mrubens]

Promote v0.30.1

Frozen at 9de08574a9d7e9db0497e34ba13ae5f4af612b01 — the commit where 0.30.1 was versioned. Commits merged to develop afterward require an explicit candidate refresh or ship in the next release.

• Merge this PR with a merge commit (do not squash or rebase).
• If multiple promote PRs are open, merge them in version order (oldest first).
• Merging publishes a GitHub Release for v0.30.1 and triggers the existing GHCR v* image publish (latest channel).
• The release/v0.30.1 branch can be deleted after this PR merges.

Changelog

0.30.1 (2026-08-02)

This patch improves custom automation scheduling and keeps Docker sandbox cleanup reliable in restricted deployments.

Highlights

• Keep Docker sandbox cleanup working through restricted socket proxies so expired orphan task networks are removed without broadening proxy permissions.
• Schedule custom automations reliably with discoverable built-in hourly, daily, and weekly presets.

Patch changes

• Keep Docker sandbox cleanup working through restricted socket proxies so expired orphan task networks are removed without broadening proxy permissions.
• Help agents schedule custom automations reliably by exposing every built-in hourly, daily, and weekly schedule preset through Roomote's management tools.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
roomote	🟢 Ready	View Preview	Aug 2, 2026, 8:23 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[roomote-community]

1 issue outstanding. See task

• apps/controller/src/compute-providers/docker-sandbox-security.ts:904 Switching from docker inspect to docker container inspect does not alter the Docker Engine API request a socket proxy authorizes: both inspect the same /containers/{id}/json endpoint. The restricted deployment will therefore still receive the 403 this patch claims to fix; identify and address the denied API endpoint or proxy policy instead. The new test only verifies the CLI argv, so it cannot demonstrate the proxy behavior.

_{Reviewed 9de0857}