[Chore] Sync published Roomote 1.3.2 metadata to develop - #2297
Merged
Conversation
Contributor
roomote-roomote
Bot
requested review from
brunobergher and
mrubens
as code owners
September 6, 2026 19:22
daniel-lxs
approved these changes
Sep 6, 2026
12 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Companion to production hotfix #2296. Copies only root
package.jsonandCHANGELOG.mdfrom its final hotfix tree. Version becomes 1.3.2; changelog includes the Fast integration schema fix and retains the already-published main-only GPT-6 Astra note from v1.3.0.Why this change was made
Keep develop's product version and release history aligned after the direct-to-main hotfix. Runtime fix #2295 already exists on develop; it is not cherry-picked again. Pending develop changesets are untouched and no version command was run on this branch.
Impact
Do not merge until #2296 has merged, Tag Product Release has succeeded, immutable v1.3.2 images exist, and the GitHub Release is published. Then squash-merge this companion so the develop release workflow sees the existing tag and does not create an incorrect Promote candidate.
Two-file exact-sync verification passed; ordinary push-hook lint, fast types and knip passed. No runtime or database changes. The open 1.4.0 release-preparation PR must be refreshed from develop after this sync.
Related PRs