gabriel / muse public
fix patch fix/release-channel-rc #1 / 1
AI Agent gabriel · 14 days ago · Jul 3, 2026 · Diff

fix: add missing rc channel to semver_channel()/ReleaseChannel

semver_channel() checked for alpha/beta/nightly prefixes but had no rc branch — a real release-candidate tag (v0.2.0-rc.1) fell through every check and was silently classified as "stable", making an rc indistinguishable from an actual stable release in any channel-based logic. Surfaced while writing docs/versioning.md (musehub repo).

- Added "rc" to ReleaseChannel and _CHANNEL_MAP/_CHANNELS. - Reordered semver_channel()'s checks to match the documented maturity order (nightly < alpha < beta < rc < stable). - Updated an existing test that had literally codified the bug as expected behavior (test_rc_defaults_to_stable) to assert the correct behavior instead; added a new test for genuinely unrecognized prefixes still defaulting to stable. - Updated --channel help text and module docstrings to list rc.

73/73 tests pass, zero regressions, zero new mypy errors (confirmed against baseline).

sha256:254e662fa9d2be172cd4d0ad512b1a7a2cba596ec61b3d974053fccb83c57288 sha
+2 ~6 −1 symbols
3 changed · 1120 in snapshot files
sha256:3c3a10b18e0a3d0895ee059b25c6a2b3cd37e007f5185497e5e33c87908c2ef2 snapshot
+2
symbols added
~6
symbols modified
−1
symbol removed
3
files changed
1120
files in snapshot
0
dead code introduced
Semantic Changes 9 symbols
~ muse/cli/commands/release.py .py 2 symbols modified
~ tests/test_release.py .py 2 symbols added, 1 symbol removed, 1 symbol modified
test_rc_defaults_to_stable method method test_rc_defaults_to_stable L250–258
+ test_rc_channel method method test_rc_channel L250–257
+ test_unrecognized_prefix_defaults_to_stable method method test_unrecognized_prefix_defaults_to_stable L259–267
Files Changed
~3
1120 in snapshot
← Older Oldest on fix/release-channel-rc
All commits
Newer → Latest on fix/release-channel-rc

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:254e662fa9d2be172cd4d0ad512b1a7a2cba596ec61b3d974053fccb83c57288 --body "your comment"