What problem are you trying to solve?
Running via uv run mr-manager is inconvenient. Users should run mr-manager directly after installation.
Proposed solution
Build release workflow producing distributable artifacts and publish process docs.
Support distribution via Homebrew (macOS), APT package path for Linux, and Python channels (PyPI/pipx).
Add versioning, changelog gating, signed tags/releases, and installation instructions per channel.
Alternatives considered
Python-only distribution, manual releases, platform-specific scripts.
Expected impact
Simple global install, broader adoption, and reproducible releases.
Relevant config/code snippet
What problem are you trying to solve?
Running via
uv run mr-manageris inconvenient. Users should runmr-managerdirectly after installation.Proposed solution
Build release workflow producing distributable artifacts and publish process docs.
Support distribution via Homebrew (macOS), APT package path for Linux, and Python channels (PyPI/pipx).
Add versioning, changelog gating, signed tags/releases, and installation instructions per channel.
Alternatives considered
Python-only distribution, manual releases, platform-specific scripts.
Expected impact
Simple global install, broader adoption, and reproducible releases.
Relevant config/code snippet