gabriel / musehub public
docs docs/decouple-muse-musehub-versioning #1 / 1
AI Agent gabriel · 5 days ago · Sep 18, 2026 · Diff

docs: decouple muse and musehub version bumps from the release flow

Both repos previously shared one version string, forced-bumped together on every release. Dropped that convention: it kept forcing meaningless, empty-diff version bumps on whichever repo hadn't actually changed (most recently, muse's musehub#221 hub-scoping registration fix, which touched zero musehub code). There is also no technical coupling requiring it -- install.sh's served version comes from scanning uploaded tarballs by mtime (_latest_published_muse_version() in musehub/api/routes/musehub/install.py), falling back to musehub's own package version only if no tarball has ever been uploaded.

muse and musehub now version independently, matching the standard CLI/server pattern (git/GitHub, kubectl/API server, Terraform CLI/Terraform Cloud). Updated .museagent.md and docs/deploy.md accordingly.

sha256:d62b94b7068530fe28ffa1e09ebf27139d0461129490c9b01ae71b4467f51c51 sha
sha256:0915a2b821db881a303a989958a7cf330ea28b4cf2bb622cd3646e443aa726f6 parent
~5 symbols
sha256:0d8f0e331ad19ae578d0934ad4aab04144891e0701cc04beb3c6351f77afbacc snapshot
~5
symbols modified
0
dead code introduced
Semantic Changes 5 symbols
~ .museagent.md .md 3 symbols modified
~ musehub — Agent Configuration
~ Repo-Specific Notes
~ Deploying MuseHub and publishing a new Muse CLI build
~ docs/deploy.md .md 2 symbols modified
~ Deploy Runbook
~ Standard release flow
← Older Oldest on docs/decouple-muse-musehub-versioning
All commits
Newer → Latest on docs/decouple-muse-musehub-versioning

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:d62b94b7068530fe28ffa1e09ebf27139d0461129490c9b01ae71b4467f51c51 --body "your comment"