[Chore] Add Changesets-based develop to main release workflow - #38
Merged
Conversation
Author
|
No code issues found. See task
|
roomote-roomote-v1
Bot
force-pushed
the
chore/release-workflow-changesets
branch
from
July 9, 2026 16:10
ee5ec44 to
1db402c
Compare
Wire optional Changesets, Version/Promote PR automation, v* GitHub Releases on main, and worker prerelease guards into the existing GHCR publish path.
List every workspace package in the changesets fixed group (globs are not expanded) so versions stay lockstep, and create the product GitHub Release only after publish-ghcr has verified roomote-app and roomote-worker images.
Fail closed in tag-release.yml when the bot token is missing instead of pushing v* with GITHUB_TOKEN, which never retriggers publish-ghcr or the post-image GitHub Release job and can leave a version stuck.
roomote-roomote-v1
Bot
force-pushed
the
chore/release-workflow-changesets
branch
from
July 9, 2026 16:27
1db402c to
67caf95
Compare
Merge origin/develop into the Changesets release branch, keep create-github-release alongside notify-ops (drop removed deploy-preview bits), accept agent-guidance deletion, document main merge-only / develop squash-only, and seed product versions at 0.0.1 so the first Version PR becomes 0.0.2.
Contributor
|
No new code issues found. Both previously flagged issues are resolved in
|
Contributor
|
Resolved merge conflicts against current
|
…ases Pin checkout, changesets/action, setup-buildx, and login-action to commit SHAs already used in CI. Fix aggregate-changelog so title intro prose stays above newly inserted release sections.
mrubens
marked this pull request as ready for review
July 10, 2026 22:21
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
July 10, 2026 22:21
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
2 participants
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
Adds a single-product Changesets release workflow for promoting
develop→mainand cutting semantic product tags:0.0.1versions across the monorepo (first Version PR patch →0.0.2) and installs@changesets/cliwith afixed: ["@roomote/*"…]package list by name.developpushes,release.ymlopens/refreshes a Release Roomote Version PR viachangesets/action, then a Promote vX.Y.Z PR tomainwhen the product version is untagged and no changesets remain.mainpushes,tag-release.ymlcreates annotatedvX.Y.Ztags (requiresRELEASE_BOT_TOKEN) sopublish-ghcr.ymlcan publish production images +latest.publish-ghcr.ymlcreates the GitHub Release only after bothroomote-appandroomote-workermulti-arch images exist for the tag (keepsreleases/latesthonest). Keeps current develop notify-ops hook; does not revive removed preview/Railway deploy jobs.CONTRIBUTING.md+.changeset/README.md(main = merge-only, develop = squash-only). Dropped links to deleted.agent-guidance/.Why this change was made
Roomote needed a repeatable product version and promote path onto refreshed
develop, with version lineage aiming at 0.0.2 after existingv0.0.1.Impact
Operators get Version → Promote → tag → image → GitHub Release automation. Self-host
releases/lateststays tied to product tags whose images are ready. No end-user product UI change.Merge notes
develop(develop branch rules).RELEASE_BOT_TOKENis set before first promote to main.