Skip to content

Promote v1.19.2 to production - #3569

Merged
mrubens merged 2 commits into
mainfrom
release/v1.19.2
Oct 23, 2026
Merged

mrubens merged 2 commits into
mainfrom
release/v1.19.2

Conversation

@mrubens

@mrubens mrubens commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Promote v1.19.2

Frozen at 59aea4a107bdf29e26d86ddfbf24741d48622041 — the commit where 1.19.2 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.2 and triggers the existing GHCR v* image publish (latest channel).
  • The release/v1.19.2 branch can be deleted after this PR merges.

Changelog

1.19.2 (2026-10-22)

Roomote 1.19.2 lets you continue tasks saved before an upgrade without losing access to their saved work.

Highlights

  • Resume saved tasks after an upgrade instead of encountering a worker installation failure caused by an older snapshot image.

Patch changes

  • Follow-ups can now resume tasks saved before a Roomote upgrade instead of failing during worker installation because the task snapshot was created with an older release. Worker startup warns about the older snapshot image and continues while still requiring the installed worker to match the application release.

mrubens and others added 2 commits October 22, 2026 18:21
A restored task snapshot keeps the image the task started on, so its baked
worker release trails the deployment after every upgrade. install-worker.sh
treated that drift as fatal, so follow-ups on any task that slept before an
upgrade failed during worker install. Task snapshots hold the task's files
and cannot boot fresh, so warn and continue; the worker must still match the
application release.

Co-authored-by: Matt Rubens <2600+mrubens@users.noreply.github.com>
Co-authored-by: @mrubens <2600+mrubens@users.noreply.github.com>
@roomote-community

roomote-community Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

No code issues found. See session

Reviewed the worker compatibility change, snapshot bootstrap context, regression coverage, and release documentation/version updates. Baked-image release drift now warns while an application-release mismatch remains fatal. Deployment artifact checks and docs validation passed; other CI checks were still running when inspected. Repository validation suites were left to CI.

Reviewed 59aea4a

@mrubens
mrubens merged commit 3a05d8f into main Oct 23, 2026
72 of 73 checks passed
@mrubens
mrubens deleted the release/v1.19.2 branch October 23, 2026 03:48

This branch was successfully deployed

1 active deployment
staging - apps/docs — 59aea4a1 Deployed Oct 22, 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