Skip to content

feat(cli): unify runtime on project venv and global CLI entry#83

Merged
duguwanglong merged 3 commits intomainfrom
optimize/unify-single-venv-cli
Apr 10, 2026
Merged

feat(cli): unify runtime on project venv and global CLI entry#83
duguwanglong merged 3 commits intomainfrom
optimize/unify-single-venv-cli

Conversation

@xiami762
Copy link
Copy Markdown
Contributor

  • Prefer .venv for Python subprocess and flocks CLI resolution
  • Refresh ~/.local/bin flocks (symlink or Windows .cmd) on startup and after updates; uninstall legacy uv tool install when present
  • Restart after update via .venv python -m flocks.cli.main
  • Align install scripts and npm wrapper with global flocks-first flow
  • Run legacy task migration before backend spawn

xiami762 added 3 commits April 10, 2026 11:32
- Prefer .venv for Python subprocess and flocks CLI resolution
- Refresh ~/.local/bin flocks (symlink or Windows .cmd) on startup and after
  updates; uninstall legacy uv tool install when present
- Restart after update via .venv python -m flocks.cli.main
- Align install scripts and npm wrapper with global flocks-first flow
- Run legacy task migration before backend spawn

Made-with: Cursor
- Write flocks.cmd with OEM encoding (UTF-8 fallback) in updater and installer
- On locked flocks.exe, rename to .exe.bak instead of failing silently
- Harden install.ps1 uv tool list/uninstall error handling

Made-with: Cursor
Avoid invoking flocks.exe from the venv on Windows so the console script
is not locked during live uv sync upgrades. Split tests for Unix vs
Windows resolution paths.

Made-with: Cursor
@xiami762 xiami762 requested a review from duguwanglong April 10, 2026 10:12
@duguwanglong duguwanglong merged commit e4cbb25 into main Apr 10, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants