Major improvements to plugin setup experience: Setup Commands: - Redesign /initial-setup as interactive wizard (MCP + system + project config) - Add /project-init for quick project-only setup - Add /project-sync for handling repository moves/renames - Add Gitea API validation to auto-fill org/repo when verified Configuration Changes: - Move GITEA_ORG from system to project level (supports multi-org users) - System config now only contains GITEA_URL and GITEA_TOKEN - Project .env now contains GITEA_ORG and GITEA_REPO Automation: - Add SessionStart hook for projman and pr-review - Automatically detects git remote vs .env mismatch - Warns user to run /project-sync when mismatch found Documentation: - Unify configuration docs (remove duplicate in plugins/projman) - Add flow diagrams to CONFIGURATION.md - Add setup script review guidance to UPDATING.md - Update COMMANDS-CHEATSHEET.md with new commands and hooks Files added: - plugins/projman/commands/project-init.md - plugins/projman/commands/project-sync.md - plugins/projman/hooks/hooks.json - plugins/pr-review/commands/initial-setup.md - plugins/pr-review/commands/project-init.md - plugins/pr-review/commands/project-sync.md - plugins/pr-review/hooks/hooks.json - plugins/cmdb-assistant/commands/initial-setup.md Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
4.2 KiB
Updating Leo Claude Marketplace
This guide covers how to update your local installation when new versions are released.
Quick Update
# 1. Pull latest changes
cd /path/to/leo-claude-mktplace
git pull origin main
# 2. Run post-update script
./scripts/post-update.sh
Then restart your Claude Code session to load any changes.
What the Post-Update Script Does
- Updates Python dependencies for MCP servers (gitea, netbox)
- Shows recent changelog entries so you know what changed
- Validates your configuration is still compatible
After Updating: Re-run Setup if Needed
When to Re-run /initial-setup
You typically don't need to re-run setup after updates. However, re-run if:
- Changelog mentions new required environment variables
- Changelog mentions breaking changes to configuration
- MCP tools stop working after update
For Existing Projects
If an update requires new project-level configuration:
/project-init
This will detect existing settings and only add what's missing.
Manual Steps After Update
Some updates may require manual configuration changes:
New Environment Variables
If the changelog mentions new environment variables:
- Check the variable name and purpose in the changelog
- Add it to the appropriate config file:
- System variables →
~/.config/claude/gitea.envornetbox.env - Project variables →
.envin your project root
- System variables →
New MCP Server Features
If a new MCP server tool is added:
- The post-update script handles dependency installation
- Check plugin documentation for usage
- New tools are available immediately after session restart
Breaking Changes
Breaking changes will be clearly marked in CHANGELOG.md with migration instructions.
Setup Script and Configuration Workflow Changes
When updating, review if changes affect the setup workflow:
-
Check for setup command changes:
git diff HEAD~1 plugins/*/commands/initial-setup.md git diff HEAD~1 plugins/*/commands/project-init.md git diff HEAD~1 plugins/*/commands/project-sync.md -
Check for hook changes:
git diff HEAD~1 plugins/*/hooks/hooks.json -
Check for configuration structure changes:
git diff HEAD~1 docs/CONFIGURATION.md
If setup commands changed:
- Review what's new (new validation steps, new prompts, etc.)
- Consider re-running
/initial-setupor/project-initto benefit from improvements - Existing configurations remain valid unless changelog notes breaking changes
If hooks changed:
- Restart your Claude Code session to load new hooks
- New hooks (like SessionStart validation) activate automatically
If configuration structure changed:
- Check if new variables are required
- Run
/project-syncif repository detection logic improved
Troubleshooting Updates
Dependencies fail to install
# Rebuild virtual environment
cd mcp-servers/gitea
rm -rf .venv
python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt
deactivate
Configuration no longer works
- Check CHANGELOG.md for breaking changes
- Run
/initial-setupto re-validate and fix configuration - Compare your config files with documentation in
docs/CONFIGURATION.md
MCP server won't start after update
- Check Python version:
python3 --version(requires 3.10+) - Verify venv exists:
ls mcp-servers/gitea/.venv - Restart Claude Code session
- Check logs for specific errors
New commands not available
- Restart your Claude Code session
- Verify the plugin is still installed
- Check if the command requires additional setup
Version Pinning
To stay on a specific version:
# List available tags
git tag
# Checkout specific version
git checkout v3.0.0
# Run post-update
./scripts/post-update.sh
Checking Current Version
The version is displayed in the main README.md title and in CHANGELOG.md.
# Check version from changelog
head -20 CHANGELOG.md
Getting Help
- Check
docs/CONFIGURATION.mdfor setup guide - Check
docs/COMMANDS-CHEATSHEET.mdfor command reference - Review
CHANGELOG.mdfor recent changes - Search existing issues in Gitea