personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(projman): correct Phase 2 setup to use setup-venvs.sh and .venv path #451

Merged
lmiranda merged 1 commits from fix/setup-workflows-venv-path into development 2026-02-07 23:07:21 +00:00
Conversation 0 Commits 1 Files Changed 1 +22 -10
lmiranda commented 2026-02-07 23:06:57 +00:00
Owner
Copy Link

Summary

  • Replace hardcoded single-server venv/ creation in Phase 2 (MCP Server Setup) with a call to scripts/setup-venvs.sh, which handles all 5 MCP servers with cached venvs and hash-based change detection
  • Fix directory name from venv/ to .venv/ to match what setup-venvs.sh and setup.sh actually create
  • Add verification step (--check flag) and fallback manual instructions

Test plan

  • Run /projman setup --full and confirm Phase 2 invokes setup-venvs.sh
  • Verify all 5 MCP servers report OK via setup-venvs.sh --check
  • Confirm no bare venv/ references remain in setup-workflows.md
  • Marketplace validation passes (./scripts/validate-marketplace.sh)

Generated with Claude Code

## Summary - Replace hardcoded single-server `venv/` creation in Phase 2 (MCP Server Setup) with a call to `scripts/setup-venvs.sh`, which handles all 5 MCP servers with cached venvs and hash-based change detection - Fix directory name from `venv/` to `.venv/` to match what `setup-venvs.sh` and `setup.sh` actually create - Add verification step (`--check` flag) and fallback manual instructions ## Test plan - [ ] Run `/projman setup --full` and confirm Phase 2 invokes `setup-venvs.sh` - [ ] Verify all 5 MCP servers report OK via `setup-venvs.sh --check` - [ ] Confirm no bare `venv/` references remain in setup-workflows.md - [ ] Marketplace validation passes (`./scripts/validate-marketplace.sh`) Generated with [Claude Code](https://claude.com/claude-code)
lmiranda added 1 commit 2026-02-07 23:06:58 +00:00
fix(projman): correct Phase 2 setup to use setup-venvs.sh and .venv path 16bf1b969d 
- Replace hardcoded single-server venv/ creation with setup-venvs.sh call
- Fix directory name from venv/ to .venv/ matching actual scripts
- Add fallback manual steps if setup-venvs.sh fails
- Add verification step using --check flag

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
lmiranda merged commit bbce9ed321 into development 2026-02-07 23:07:21 +00:00
lmiranda deleted branch fix/setup-workflows-venv-path 2026-02-07 23:07:21 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#451
Delete Branch "fix/setup-workflows-venv-path"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?