feat(installer): bring channel-aware installer/updater onto rc (cherry-pick #54) - #55
Merged
Conversation
Adds a stable (default) / rc release channel: RC tags publish as GitHub prereleases; install.sh + maestro-relay-ctl gain MAESTRO_RELAY_CHANNEL / 'channel' subcommand / 'update --rc'. Explicit version pins preserved; channel persisted on install; invalid channels rejected/normalized. Review findings addressed.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
chr1syy
added a commit
that referenced
this pull request
Jun 30, 2026
Second release candidate — folds in #55 so the RC tarball itself carries the channel-aware install.sh + maestro-relay-ctl (channel / update --rc), on top of the Teams (Phase 1) and Telegram providers. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
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.
Bring the channel-aware installer onto
rcCherry-picks #54 (the opt-in RC release channel) from
mainontorc, so the rc branch — and therefore RC release tarballs cut from it — carry the channel-awareinstall.sh+maestro-relay-ctl, not just therelease.ymlprerelease marking that rc already had.Why
mainandrchad diverged:maingot #54's channel installer, butrconly got therelease.ymlprerelease change (added when cuttingv0.5.0-rc.1). That left a rough edge — the RC tarball's bundledmaestro-relay-ctllacked thechannel/update --rccommands, and$CONFIG_DIR/channelwritten at install wasn't read back. This closes that gap so an RC install can stay on the rc channel acrossupdate.What's included (from #54, final squashed form)
install.sh:MAESTRO_RELAY_CHANNEL(stable|rc), channel-awareresolve_release, validates the channel up front, persists it to$CONFIG_DIR/channelon install.maestro-relay-ctl:update --rc/--stable,channelsubcommand, explicitMAESTRO_RELAY_VERSIONpins preserved, unknown channels normalized to stable.The one conflict (the
deployusage line) was resolved to keep rc's multi-provider wording and the newupdate/channellines.release.ymlalready had the identical prerelease line (deduped to one).Verification
bash -nclean on both scripts;channelset/read smoke-testednpm run buildclean; 316/316 tests passrelease.ymlhas exactly oneprerelease:line🤖 Generated with Claude Code