Skip to content

Promote v1.19.5 to production - #3623

Merged
mrubens merged 8 commits into
mainfrom
release/v1.19.5
Oct 29, 2026
Merged

mrubens merged 8 commits into
mainfrom
release/v1.19.5

Conversation

@mrubens

@mrubens mrubens commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Promote v1.19.5

Frozen at 07e17823d8f8ada25398ae37723f7b6de0568a5c — the commit where 1.19.5 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).
  • Monitor CI and reviews on this PR's current head, not only the release-preparation PR. Unresolved findings and missing required approvals remain blockers even with green CI.
  • After a refresh or CI reconciliation, re-check the new head; monitoring never authorizes merging or publication.
  • Merging publishes a GitHub Release for v1.19.5 and triggers the existing GHCR v* image publish (latest channel).
  • The release/v1.19.5 branch can be deleted after this PR merges.

Changelog

1.19.5 (2026-10-29)

Roomote 1.19.5 improves GitHub work across organizations and restores integration-key access for scheduled and manually run custom automations.

Highlights

  • Connect additional GitHub organizations and use HTTPS Git across repositories available to a task.
  • Start pull request reviews reliably when multiple GitHub organizations are connected.
  • Use existing integration keys in scheduled and manually run custom automations.

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.

roomote-roomote Bot and others added 8 commits October 27, 2026 09:42
…3603)

* test(worker): expect shipped Kimi K3.1 provider routes

* test(runtime): expect Kimi K3.1 routes in helper config

---------

Co-authored-by: @daniel-lxs <57051444+daniel-lxs@users.noreply.github.com>
* improve: make self-hosting the public getting-started path

* docs: remove hosted branding from in-app release history

---------

Co-authored-by: Roomote <roomote@roomote.dev>
Update undici to 7.30.1 and qs to 6.16.1 through shared overrides, direct dependency ranges, and lockfile resolutions. Preserve the existing release-age policy.
Co-authored-by: @mrubens <2600+mrubens@users.noreply.github.com>
@roomote-community

roomote-community Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

No code issues found. See session

Reviewed the release diff, including cross-installation Git credentials and refresh, automation integration-key authority, dependency updates, and self-hosting documentation/UI changes. Current-head tests, lint, type checks, Knip, and docs validation passed; build and JavaScript/TypeScript CodeQL jobs were still running when checked. No approval submitted.

Reviewed 07e1782

@mrubens
mrubens merged commit a1d6a79 into main Oct 29, 2026
56 checks passed
@mrubens
mrubens deleted the release/v1.19.5 branch October 29, 2026 12:19

This branch was successfully deployed

1 active deployment
staging - apps/docs — 07e17823 Deployed Oct 29, 2026 by mintlify[bot]
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