chore: sync musehub version to 0.2.1rc2, matching muse's current release
musehub's own pyproject.toml version drives the static MUSE_VERSION template global (musehub/protocol/version.py), which the getting-started docs page uses to show illustrative example output like `muse --version` → `muse {{ MUSE_VERSION }}`. install.sh itself already resolves the real latest published tarball dynamically (by mtime scan of the releases dir) and was unaffected by this — a real install already gets 0.2.1rc2 correctly. But the docs page's *illustrative* output text still showed the stale 0.2.0.dev4, since it reads musehub's own static version rather than the dynamic resolution install.sh uses.
Historically the two were kept in sync (both were 0.2.0.dev4 together) — restoring that convention rather than introducing new template plumbing to expose the dynamic latest-tarball version separately. Requires a redeploy to take effect (protocol/version.py reads pyproject.toml once at process start, via importlib.metadata falling through to a direct regex read since musehub isn't pip-installed as a package in its own container).
Semantic Changes
2 symbols
Files Changed
~1
1071 in snapshot
0 comments
muse hub commit comment sha256:157f9f496d3fde4cb4475d3ca4880cdde56a666776a46113095695c3a74c07f6 --body "your comment"
No comments yet. Be the first to start the discussion.