Updates & Maintenance¶
Keep HoloViz MCP up to date to ensure you have the latest features, bug fixes, and documentation.
Update the Python Package¶
With uv (Recommended)¶
Update the HoloViz MCP package:
With pip¶
With conda/mamba¶
Update the Documentation Index¶
After updating the package, refresh the documentation index:
This ensures you have the latest documentation from HoloViz projects.
Combined Update¶
For convenience, update both the package and documentation:
Update Docker Image¶
Pull Latest Image¶
Update Running Container¶
If using Docker Compose:
Update Documentation in Container¶
Run the update command in the container:
Or set UPDATE_DOCS=true when starting:
docker run -it --rm \
-e UPDATE_DOCS=true \
-v ~/.holoviz-mcp:/root/.holoviz-mcp \
ghcr.io/marcskovmadsen/holoviz-mcp:latest
Check Versions¶
Check Package Version¶
Or with pip:
Check Documentation Index Version¶
The documentation index includes version information in ~/.holoviz-mcp/.
Update Frequency¶
Recommended Schedule¶
- Package Updates: Monthly or when new features are released
- Documentation Updates: Weekly or before starting a new project
- Docker Images: Pull latest before each use
When to Update¶
Update when:
- New HoloViz releases are announced
- You encounter bugs that may be fixed in newer versions
- New Panel extensions are released
- Documentation seems outdated
Rollback¶
Rollback Package¶
If an update causes issues, rollback to a previous version:
Replace 0.1.0 with the desired version.
Restore Documentation Index¶
If the documentation index gets corrupted:
Automatic Updates¶
GitHub Dependabot¶
If using HoloViz MCP in a project, configure Dependabot:
# .github/dependabot.yml
version: 2
updates:
- package-ecosystem: "pip"
directory: "/"
schedule:
interval: "weekly"
Maintenance Tasks¶
Clean Up Old Data¶
Remove unused data:
Verify Installation¶
After updates, verify everything works:
Next Steps¶
- Troubleshooting: Fix update issues
- Configuration: Customize after updates