chore: bump version to 0.2.1rc1 for release candidate 1
Cutting an RC rather than going straight to stable 0.2.1: it's been ~2 months since the last real publish (v0.2.0-nightly.4, 2026-07-09), and the intervening work includes genuinely risky changes — most notably a proposal-merge state-persistence bug (musehub staging #182) that was contained but not fully root-caused. Baking on staging as an RC before promoting to stable.
sha256:a339c969d43e25384ad115786d27d3dd7a849f85ec41ac1afc491bc337f20d51
sha
~2
symbols
1 changed · 1164 in snapshot
files
sha256:6c3312c818a00aa09d1b8140c8fb165be19e621817e62cda67672c303340c02b
snapshot
~2
symbols modified
1
file changed
1164
files in snapshot
0
dead code introduced
Semantic Changes
2 symbols
Files Changed
~1
1164 in snapshot
~1
1164 in snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:a339c969d43e25384ad115786d27d3dd7a849f85ec41ac1afc491bc337f20d51 --body "your comment"
No comments yet. Be the first to start the discussion.