[roomote-roomote]

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

What changed

Prepare the approved normal patch release 1.20.0 → 1.20.1 from develop 345f05ee552f3ea4221d701c37a500f80aade0ea. Generated the root version and changelog with pnpm run version, consumed all four temporary patch changesets, and polished the in-app summary and highlights.

The audited range contains #3646, #3666, #3645 and #3674: repairs to existing Slack, Copilot and GitHub task behavior, with no new capabilities or breaking changes. No pending changesets existed before preparation. PR authors are a listed code owner or the Roomote bot; no eligible external contributor or linked issue-reporter credits were found.

Highlights

• Restore GitHub Copilot GPT-5.x task helpers that failed on an unsupported endpoint.
• Keep available Slack history when a busy channel cannot be read completely in one request.
• Avoid false lost-access reports for private Slack conversations and false refusals of authorized GitHub actions.

Patch changes

• GitHub Copilot GPT-5.x task helpers use the correct inference endpoint instead of failing on requests sent to an unsupported endpoint.
• Coding tasks recognize their authorized GitHub write path when integration tools are read-only, avoiding false refusals to carry out requested pull request updates, comments, or workflow actions.
• Slack channel history reads return accumulated messages with explicit partial-result and continuation information instead of timing out and losing all results in busy channels.
• Slack destination guidance distinguishes unlisted private channels from lost access and directs replies, including automation results, to the current conversation without requiring standalone channel discovery.

Public documentation coverage

No new discoverability or configuration feature was introduced. Reviewed all four fixes and their existing guides:

• Slack discovery and current-conversation replies: reuse the exact correction from open [Docs] Clarify Slack destination discovery and current-conversation replies #3669 in Sessions and Slack. Private channels are absent from standalone lookup, and replies to the current conversation or configured automation report channel do not depend on that lookup. [Docs] Clarify Slack destination discovery and current-conversation replies #3669 remains separately owned; this release does not merge or close it.
• Slack bounded history: existing Slack/session guides describe bounded reads; runtime tool guidance carries partial-result continuation details. No new setup prerequisite.
• Copilot task-helper routing: GitHub Copilot setup, model selection and permissions remain accurate; the repair adds no configuration.
• GitHub task writes: GitHub source control already describes branch/PR work and Actions/Workflows write permissions; corrected runtime guidance requires no public setup change.
• Existing Slack, Copilot and GitHub provider guides and overviews use source-backed marks; no provider, navigation or logo additions needed.

How it was tested

• pnpm run version generated 1.20.1 from four patch notes.
• Release-invariant assertions passed: four generated patch bullets, no empty minor/major sections, all pending notes consumed, .changeset/README.md preserved, previous changelog history byte-for-byte preserved, and only the root version/changelog plus two intended docs pages changed. Workspace package versions remain untouched.
• git diff --check passed; inspected the full PR diff and exact reused docs correction.
• Opened both changed pages in the running Mintlify browser preview and confirmed the new private-channel guidance rendered. No screenshots or live Slack/Copilot provider checks are claimed.
• Ordinary pre-commit hooks passed formatting and Judgement (8 judgments).
• Ordinary push hook ran exactly once and passed: oxlint, residual web/worker ESLint, all 27 fast typecheck tasks and Knip. Turbo reported existing circular package dependencies and Knip a non-failing Mint ignore-binary hint.
• Per the release workflow, full release-script, Vitest, formatting-inclusive static and docs-validation suites were left to PR CI rather than run again manually. CI and Docs must succeed before merge, alongside required reviews.

Squash-merging this preparation PR cuts the release and automatically opens the frozen Promote v1.20.1 to production PR against main. That candidate needs its own current-head CI and review validation. Preparation authorizes no merge, promotion, auto-merge, tag, publishing, deployment or workflow dispatch. If develop advances before merge, re-audit and regenerate from its new tip.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description
  • Uses the release skill's required title exception: Release Roomote 1.20.1.
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally
  • Normal fast equivalents passed through the ordinary push hook; full formatting-inclusive commands are reserved for CI.
• I added tests or included a clear manual validation note above
• I removed secrets, tokens, private keys, and customer data from code, logs, and screenshots
• If this change should appear in the changelog, I ran pnpm changeset
  • Authored four single-package patch inputs directly, then consumed them through canonical pnpm run version.

[roomote-community]

No code issues found. See session

Reviewed all four changed files, release version/changelog consistency, the four underlying fix commits, and Slack destination guidance against the implementation. Historical release notes and workspace package versions are unchanged.

Current-head tests, lint, type checks, docs validation, CodeQL, and compatibility checks passed. The app Docker build was still running when checked. No local validation suites were rerun.

_{Reviewed a13cf7f}