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

fix(post-update): create missing venvs instead of just warning #209

Merged
lmiranda merged 1 commits from fix/post-update-create-venvs into development 2026-01-27 15:51:40 +00:00
Conversation 0 Commits 1 Files Changed 1 +36 -12
lmiranda commented 2026-01-27 15:42:40 +00:00
Owner
Copy Link

Summary

  • post-update.sh now creates missing venvs automatically instead of just warning
  • Added viz-platform and contract-validator to the MCP server update list
  • Installs editable packages when pyproject.toml exists

Test plan

  • Verified script creates missing venvs on installed marketplace
  • All 5 MCP servers now have venvs after running post-update.sh

🤖 Generated with Claude Code

## Summary - post-update.sh now creates missing venvs automatically instead of just warning - Added viz-platform and contract-validator to the MCP server update list - Installs editable packages when pyproject.toml exists ## Test plan - [x] Verified script creates missing venvs on installed marketplace - [x] All 5 MCP servers now have venvs after running post-update.sh 🤖 Generated with [Claude Code](https://claude.ai/claude-code)
lmiranda added 1 commit 2026-01-27 15:42:41 +00:00
fix(post-update): create missing venvs instead of just warning 08e1dcb1f5 
Previously post-update.sh would only warn when venvs were missing,
requiring a separate setup.sh run. Now it automatically creates
missing venvs and installs dependencies including editable packages.

Also added viz-platform and contract-validator to the update list.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda merged commit bbb822db16 into development 2026-01-27 15:51:40 +00:00
lmiranda deleted branch fix/post-update-create-venvs 2026-01-27 15:51:40 +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#209
Delete Branch "fix/post-update-create-venvs"

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?