Skip to content

Release Roomote 1.13.2 - #3246

Merged
mrubens merged 3 commits into
developfrom
feature/roomote-1-13-2-release-2z7bkvph9rx6s
Sep 26, 2026
Merged

mrubens merged 3 commits into
developfrom
feature/roomote-1-13-2-release-2z7bkvph9rx6s

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

​Opened on behalf of @mrubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

Prepare the normal Roomote 1.13.2 release from published v1.13.1.

  • Bump the single product version in the root package.json from 1.13.1 to 1.13.2.
  • Generate the top CHANGELOG.md section with the final patch notes and in-app summary/highlights.
  • Consume the pending setup-completion changeset.
  • Update public judgment-model guidance to describe the evaluated policy and safe fallback behavior.

Patch changes

  • The Roomote judgment model now supports evaluated Session status classification when enabled, while decisions outside its policy keep the existing safe fallback.
  • Saved-to-memory events in Session and task transcripts now use the same expandable tool row as other tool activity, preserving the saved facts and memory label.
  • Reopening a completed setup link now returns admins to Home instead of leaving the setup page on a loading spinner.

Why this change was made

The latest published release is v1.13.1, and its tag is published and reachable from main. The audited develop range contains only backward-compatible fixes and improvements, and all three consumed changesets are patch, so the requested patch release is 1.13.2.

The test-only packages/types consolidation was audited and intentionally ships without a changelog bullet. The Auto tool-approval and custom automation launch-criteria coverage in the judgment-model change is explicitly internal-nightly, so it is not included in public release notes or public feature documentation.

Impact

Users get safer evaluated Session status judgments with the self-hosted Roomote model, consistent saved-memory transcript presentation, and reliable navigation when reopening a completed setup link. Existing behavior remains the fallback for unsupported or uncertain judgment decisions.

Local validation passed through the one ordinary pre-push gate: oxlint, residual lint, fast type checks across 27 packages, and Knip. git diff --check and release artifact assertions also passed. Knip reported the existing Mint binary configuration hint only. Per the repository release guidance, release-script tests and docs validation are left to the PR workflows rather than rerun manually.

Public docs coverage

  • Session status judgment: apps/docs/models.mdx now limits the Roomote model claim to its evaluated policy, and apps/docs/self-hosting.mdx documents the same safe fallback behavior. apps/docs/fast-sessions.mdx already describes the Session status experiment, so no navigation change is needed.
  • Saved-memory transcript rows: no docs update is needed; this is a presentation consistency improvement that preserves the existing label and saved facts.
  • Completed setup redirect: no docs update is needed; this fixes an intermittent setup navigation symptom without changing the setup workflow.

Release boundary

Squash-merging this PR cuts Roomote 1.13.2 on develop and lets CI freeze release/v1.13.2 and open the separate Promote v1.13.2 to production PR against main. This preparation PR does not merge, promote, tag, publish, deploy, or modify main.

@roomote-community

roomote-community Bot commented Sep 26, 2026 •

Copy link
Copy Markdown
Contributor

No code issues found. See task

Reviewed b6ad26f

@roomote-roomote
roomote-roomote Bot marked this pull request as ready for review September 26, 2026 03:28
@mrubens
mrubens merged commit 449a2e7 into develop Sep 26, 2026
18 checks passed
@mrubens
mrubens deleted the feature/roomote-1-13-2-release-2z7bkvph9rx6s branch September 26, 2026 03:43
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