Promote v0.34.0 to production

[mrubens]

Promote v0.34.0

Frozen at 55fa64c370fb8839b127fdd031ab1eb5e344589a — the commit where 0.34.0 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.34.0 and triggers the existing GHCR v* image publish (latest channel).
• The release/v0.34.0 branch can be deleted after this PR merges.

Changelog

0.34.0 (2026-08-04)

This release adds Granola and Requesty connections, introduces Mind reader mode for expanded model thoughts, and improves task reliability across mixed-provider workspaces and chat delivery failures.

Highlights

• Connect Granola once for deployment-wide access to approved meeting notes, folders, and transcripts.
• Connect Requesty from setup or model settings with a curated catalog of current supported models.
• Expand model thought blocks by default with the optional Mind reader mode.
• Launch tasks reliably from workspaces that combine repositories across supported source-control providers.

Minor changes

• Let deployment administrators connect Granola once so Roomote can securely browse the notes, folders, and transcripts allowed by the configured API key.
• Add an optional Mind reader mode that expands LLM thought blocks by default while preserving manual conversation-level choices.
• Let users connect Requesty from setup or model settings and start with a curated catalog of current supported models.

Patch changes

• Use Roomote's stable branded Discord invite from the repository and in-app release notes.
• Keep tasks running when agents attempt to read unsupported ICO or CUR files by returning a recoverable tool error before provider submission.
• Launch tasks reliably from workspaces that combine repositories across GitHub, GitLab, Gitea, Azure DevOps, and Bitbucket with provider-scoped credentials. Thanks to @jantekb for reporting #1082.
• Require an active deployment administrator to create or update shared environments through Roomote's MCP tools.
• Stop completed chat tasks from entering repeated closeout attempts when message delivery has failed permanently.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
roomote	🟢 Ready	View Preview	Aug 4, 2026, 9:39 PM

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

[roomote-community]

2 issues outstanding. See task

• packages/cloud-agents/src/server/task-run-queue.ts:1808 Mixed-provider stamps retain only a provider per repository and then clear sourceControlHost. Repository-level source-control reads and writes deliberately ignore the scalar host for mapped repositories, so a task targeting a same-name repository on two self-hosted instances cannot disambiguate its target and fails instead of using the intended host. Persist host identity per repository with the provider map.
• packages/slack/src/slack-notifier.ts:904 A thread root can be deleted after hasMessageInThread succeeds. In that race chat.postMessage returns thread_not_found, but this is surfaced as a retryable delivery error rather than skippedMissingThreadRoot; the handler returns 502 and the agent retries an already-deleted thread instead of receiving the existing 409 terminal response. Map that threaded Slack error to the missing-root outcome.

_{Reviewed 55fa64c}