Skip to content

Promote v0.33.0 to production - #1097

Merged
mrubens merged 13 commits into
mainfrom
release/v0.33.0
Aug 4, 2026
Merged

Promote v0.33.0 to production#1097
mrubens merged 13 commits into
mainfrom
release/v0.33.0

Conversation

@mrubens

@mrubens mrubens commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Promote v0.33.0

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

Changelog

0.33.0 (2026-08-04)

This release adds new ways to connect and invoke Roomote, gives deployments clearer account-linking guidance, and improves automation and Amazon Bedrock model discovery.

Highlights

  • Start Roomote from existing Slack, Discord, and Microsoft Teams conversations with an administrator-configured emoji reaction.
  • Connect Resend with safe inspection-oriented defaults and explicit controls for sensitive actions.
  • Add deployment-specific account-linking guidance across chat, source control, and sign-in surfaces.
  • Keep Amazon Bedrock models visible and organized under one provider section in model settings.

Minor changes

  • Let administrators configure an emoji that starts Roomote from an existing Slack, Discord, or Microsoft Teams conversation, reusing the normal task flow and preserving the reacting user's account attribution.
  • Add Resend as a deployment-wide integration with inspection-oriented access by default and explicit administrator controls for sensitive email, credential, automation, contact, domain, and webhook actions.
  • Let administrators add deployment-specific account-linking guidance that appears alongside Roomote's built-in instructions in source-control comments, Discord, Telegram, and the sign-in page.

Patch changes

  • Keep Amazon Bedrock Mantle models visible after settings reload and group native Bedrock and Mantle entries under one Amazon Bedrock section instead of showing duplicate headings.
  • Make routine Discord release announcements shorter and suppress link-preview cards while keeping the release notes link available.
  • Make automations the highest-priority onboarding prompt for users who have not enabled one, and link the Automations page directly to practical Cookbook recipes.

roomote-roomote Bot and others added 13 commits August 4, 2026 10:44
Co-authored-by: Roomote <roomote@roomote.dev>
* feat: call Roomote from thread reactions

* fix: tighten reaction-trigger provider behavior

* fix: prevent automation category label clipping

* fix: filter emoji automation by category

* fix: address reaction trigger review findings

* fix: scope reaction dedupe to gateway sessions

---------

Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Roomote <roomote@roomote.dev>
* docs: add cloud agent adoption recipe

* docs: clarify cookbook recipe workflow

---------

Co-authored-by: Roomote <roomote@roomote.dev>
)

* improve: compact Discord release announcements

* refactor: split Discord release message builders

---------

Co-authored-by: Roomote <roomote@roomote.dev>
* feat: track setup funnel milestones

* fix: preserve setup milestone detection

---------

Co-authored-by: Roomote <roomote@roomote.dev>
* feat: promote automation onboarding and recipes

* ui

* test: fix CI navigation and database isolation failures

---------

Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Bruno Bergher <bruno@roocode.com>
* feat: add Resend MCP integration

* fix: disable unsafe Resend automation tools

* fix: show Resend safety defaults in catalog

* fix: close Resend permission escape paths

* fix: close remaining Resend tool escape paths

* fix: configure Resend OAuth endpoints

* fix: make Resend tool schemas Azure-compatible

* test: update Resend integration description assertion

---------

Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Bruno Bergher <bruno@roocode.com>
Co-authored-by: Matt Rubens <2600+mrubens@users.noreply.github.com>
Co-authored-by: Roomote <roomote@roomote.dev>
Co-authored-by: Matt Rubens <2600+mrubens@users.noreply.github.com>
)

Co-authored-by: Matt Rubens <2600+mrubens@users.noreply.github.com>
Co-authored-by: Matt Rubens <2600+mrubens@users.noreply.github.com>
@mintlify

mintlify Bot commented Aug 4, 2026

Copy link
Copy Markdown

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

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

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

@roomote-community

roomote-community Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

1 issue outstanding. See task

  • apps/api/src/handlers/slack/events/reactions.ts:82: The synthetic app mention reuses the reacted message's timestamp. On an active task, the Slack delivery tracker treats that timestamp as the current turn, excludes the actual reacted message from thread context, and then marks it delivered. The agent receives only Act on this, not the message or its attachments; give the synthetic turn a unique ID and explicitly include context through the target message.

Reviewed c3e7722

@mrubens
mrubens merged commit 9bc9cb8 into main Aug 4, 2026
50 checks passed
@mrubens
mrubens deleted the release/v0.33.0 branch August 4, 2026 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant