Promote v0.26.0 to production

[mrubens]

Promote v0.26.0

Candidate updated to 85c66c0e735bf372b10ec1945f65e86f05167f6d, the latest origin/develop commit at the time of refresh. The original 0.26.0 version commit was 2b21bc9f331ec857ae9991edeb34cabfcbbae9b0.

Additional candidate fixes

• Prevent duplicate GitHub follow-up quotes.

• Resume Linear sessions with the correct authorized account.

• Route the first Linear session correctly after OAuth.

• 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.26.0 and triggers the existing GHCR v* image publish (latest channel).

• The release/v0.26.0 branch can be deleted after this PR merges.

Changelog

0.26.0 (2026-07-29)

This release expands Linear and GitHub workflows, makes release information easier to find, and improves setup and task reliability.

Highlights

• Set up and manage Linear, link user accounts, and start app-mention, issue-delegation, scheduled, and direct Linear tasks.
• Create or fork a GitHub repository from Roomote, then bootstrap an empty repository and configure its environment automatically.
• Manage GitHub labels, milestones, and project status values safely from Roomote tasks.
• Find the running Roomote version easily, verify Teams credentials during setup, and start sandboxes more reliably through transient broker failures.

Minor changes

• Announce newly published Roomote releases in Discord with the release title, notes, link, timestamp, and Roomote branding when a main-channel webhook is configured.
• Set up and manage Linear from onboarding or Settings, link user accounts, and start app-mention, issue-delegation, scheduled, and direct Linear tasks with the correct workspace and account context.
• Create a new GitHub repository or fork an existing one from Roomote, then automatically detect empty repositories, add their initial commit, and configure a working environment.
• Manage GitHub labels, milestones, and project status values from Roomote tasks with scoped credentials, confirmation for destructive changes, and read-back verification.
• See the running Roomote version from the signed-in user menu, open release details, and revisit the latest What's New notice without administrator access.

Patch changes

• Hide self-hosted license controls from cloud deployments while keeping license management available to self-hosted administrators.
• Make task conversations easier to follow by showing request-input questions as distinct quoted context, refining mobile task chrome, quoting web follow-ups in GitHub replies, and keeping internal routing context out of Slack and Discord quotes.
• Retry transient compute-broker upload failures during sandbox startup so momentary upstream errors no longer prevent task environments from starting.
• Choose the model used by the Onboarding Agent when editing an existing environment, matching the model selection already available when creating one.
• Verify Microsoft Teams bot credentials with Microsoft before saving them, so a wrong app id, client secret, or tenant id fails the save with a message naming the field instead of reporting a configured bot that cannot authenticate. Teams settings now also reports when the saved credentials stop authenticating, and explains why the Teams app package cannot be pre-filled from a malformed App (Client) ID.

[roomote-roomote]

1 issue outstanding. See task

• apps/web/src/lib/server/mcp-linear.ts:175 The replay path accepts the OAuth viewer from any Linear user or organization, then consumes the original session replay and starts its task. Verify the viewer ID and organization against the replay's saved Linear identity before updating the link or resuming the session; otherwise a user who authorizes a different Linear account gets a successful but invalid link and bypasses the session identity check for that initial task.
• packages/communication/src/messages.ts:57 A claim is retained for 30 days, but every later call generates a new claim token. If a worker/request stops after moving the message into the claim key, later deliveries see the mismatched claim and return no quote, so that follow-up is suppressed until the lease expires. Make an abandoned claim recoverable (or use a short lease) before treating it as unavailable.

_{Reviewed 85c66c0}

[mintlify]

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

Project	Status	Preview	Updated (UTC)
roomote	🟢 Ready	View Preview	Jul 29, 2026, 6:21 PM

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