feat: muse release defaults to list; add muse release suggest
- bare `muse release` (no subcommand) now lists releases — same ergonomics as `muse branch` - `muse release --json` works without a subcommand - new `muse release suggest` infers next version from commit graph sem_ver_bump data: * aggregates max(sem_ver_bump) across all unreleased commits * applies pre-1.0 rules (major break → bump minor in 0.x.y, not cross 1.0) * outputs suggested_tag, inferred_bump, drivers list with breaking_changes * --base <tag> to scope from a specific release, --json for machine output - 21 tests: 6 for default-list ergonomics, 15 for suggest
sha256:443dc4faed3285a2db625b0b3345fe1c0ced2fa29191181c47f1b751d4b27a7b
sha
sha256:ef64b53636ab420b7f31432f412dc64eb9847f89186b290d48b6bc0db08027f4
snapshot
← Older
Oldest on task/release-default-and-suggest
All commits
Newer →
Latest on task/release-default-and-suggest
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:443dc4faed3285a2db625b0b3345fe1c0ced2fa29191181c47f1b751d4b27a7b --body "your comment"
No comments yet. Be the first to start the discussion.