feat: replace milestones with Muse-native release tracking via commit anchors
Delete MusehubMilestone entirely — milestones were a GitHub-ism for connecting issues to releases when the VCS lacked that link. Muse has commit_anchors on every issue; the VCS graph is the source of truth.
Changes: - Drop musehub_milestones and musehub_issue_milestones tables (migration 0036) - Remove MusehubMilestone, MusehubIssueMilestone ORM models - Remove milestone_id FK from MusehubIssue - Remove MilestoneCreate/Response/ListResponse Pydantic models - Delete milestones.py and ui_milestones.py route modules - Delete all milestone templates and macros (6 files) - Delete all milestone test files (3 files) - Add get_issue_release_context() service function: resolves commit anchors against MusehubRelease records to determine which release(s) a fix landed in - Issue detail sidebar: replace milestone card with release card showing 'landed in vX.Y.Z', 'fix on dev (unreleased)', or 'no commits yet' - Issue list: remove milestone filter, bulk milestone select, milestone sidebar - Update SCSS: add release card theme, remove all milestone styles - Clean up all milestone references from TS, docstrings, and test helpers
0 comments
muse hub commit comment sha256:79bee467f8df740a1b02378037307566416bf0639cc8f11eeeb04f58f221e1ea --body "your comment"
No comments yet. Be the first to start the discussion.