[roomote-roomote]

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

What changed

Prepare Roomote 1.19.4 → 1.19.5, using the explicitly selected patch bump. Generated the root version and changelog with pnpm run version, consumed both locally authored patch changesets, and polished the in-app summary and highlights. Workspace package versions and historical release notes are unchanged.

Audited all seven first-parent merges from published v1.19.4 (01f01c97) through develop 311726f8. No pending changesets, existing preparation/Promote PR, or newer unshipped candidate were found. Direct CODEOWNERS and author/issue checks found no eligible external acknowledgments. Test-only #3603, positioning/docs #3611, and dependency-only #3615 ship without separate changelog notes.

Patch changes

• Scheduled and manually run custom automations can now use their creator's available personal and deployment-wide integration keys instead of finding an empty integration list. New key approvals still require a human turn, and webhook-triggered runs do not receive integration keys.
• Work with GitHub repositories across organizations: Update GitHub now opens the account picker to add another installation, pull request reviews no longer fail to start when multiple organizations are connected, and tasks can clone, fetch, and push available repositories across installations using HTTPS Git. Task API and pull request delivery access retain their existing installation boundaries.

Public documentation coverage

• Cross-installation task HTTPS Git: GitHub guide, reusing [Docs] Clarify task Git access across GitHub installations #3617's exact clarification with availability changed to starting with 1.19.5. Preserves single-installation API, task delivery, and explicit-environment limits. [Docs] Clarify task Git access across GitHub installations #3617 remains open and is neither merged nor closed by this preparation.
• Adding another organization/account picker: existing GitHub setup guidance is current.
• Custom automation integration keys: existing integration-key guidance covers creator-owned scheduled/manual access, webhook exclusion, and human-only new approvals.
• Self-hosting-first entry path: getting started, first task, and self-hosting already reflect [Improve] Make self-hosting the public getting-started path #3611.
• GitHub page and source-control overview use the matching source-backed Simple Icons GitHub mark; no new logo assets or navigation entries needed.

How it was tested

• pnpm run version: generated 1.19.4 → 1.19.5 and consumed both patch inputs.
• Read-only artifact assertions passed: expected product version, no remaining changesets, exact three-file diff, unchanged historical changelog, and no workspace package version changes. git diff --check passed.
• Commit hooks passed: lint-staged formatting and Judgement (6 judgments).
• Ordinary git push origin HEAD ran the pre-push gate once: oxlint, residual web/worker ESLint, 27/27 fast typecheck tasks, and Knip passed. Non-failing hints: existing package dependency cycle and Mint ignored-binary entry.
• As directed by the release skill, did not manually duplicate release-script tests, docs validation, full product tests, or static suites. Hosted CI and Docs must succeed before merge. Browser proof is not applicable to this release-artifact and documentation-prose-only diff; no rendered-page or live GitHub/automation integration claim is made.

Squash-merging this preparation PR to develop cuts the release and automatically opens the frozen Promote v1.19.5 to production PR against main. This preparation does not authorize merging, promotion, tagging, publication, or deployment. If develop advances before merge, regenerate and re-audit from its new tip rather than merging new commits into generated artifacts.

Checklist

• The PR title follows the repo convention: [Fix], [Feat], [Improve], [Refactor], [Docs], or [Chore] followed by a user-facing description — using the release skill's explicit Release Roomote 1.19.5 title instead.
• This PR is small and scoped to one change
• pnpm lint and pnpm check-types pass locally — ordinary push gate equivalents passed; full versions remain for CI per release skill.
• 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 patch inputs and consumed them with repository-owned pnpm run version, as required for release preparation.

[roomote-community]

No code issues found. Reviewed the 1.19.5 version bump, changelog integrity, and GitHub documentation against the supporting implementation. Current-commit tests, lint, type checks, docs validation, and compatibility checks passed; the app Docker build was still running when checked. See session

_{Reviewed c8e3ef8}