Replace inline sed/jq commands in release workflow with tools/update_versions.py script that:
- Updates MCPForUnity/package.json, manifest.json, Server/pyproject.toml
- Updates version references in Server/README.md, README.md, docs/i18n/README-zh.md
- Supports --dry-run and --version flags
- Auto-detects version from package.json if not specified
- Provides better error handling and progress output
* feat: Add MCPB bundle for Claude Desktop installation
Add Model Context Protocol Bundle (MCPB) support enabling single-click
installation in Claude Desktop and other MCP hosts.
Changes:
- Add manifest.json with uvx-based server configuration
- Add icon.png for display in Claude Desktop
- Add .mcpbignore for build exclusions
- Add pre-built unity-mcp.mcpb bundle
🤖 Generated with [Claude Code](https://claude.com/claude-code)
* fix: Generate MCPB as release artifact instead of committing to repo
Address review feedback from @msanatan:
- Remove pre-built unity-mcp.mcpb and icon.png from repository
- Add tools/generate_mcpb.py script for bundle generation
- Update release.yml with new publish_mcpb job that:
- Generates bundle using generate_mcpb.py
- Uploads MCPB file as release artifact
- Update manifest.json to reference icon from docs/images/
The bundle is now generated automatically on each release,
keeping the repository clean while providing download artifacts.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
* fix: Use correct mcpb pack CLI syntax (positional args)
The mcpb CLI uses 'mcpb pack [directory] [output]' syntax,
not '--output' flag. Tested locally - bundle generates correctly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: triepod-ai <199543909+triepod-ai@users.noreply.github.com>
* chore: update version references in README files during release
- Add version update for root README.md UPM fixed version examples
- Add version update for README-zh.md UPM and pip fixed version examples
- Include README.md and README-zh.md in release commit
* Update version in README
* Update example command version
* Update simplified Chinese readme to match english one
* The readme has changed
* docs: reorganize documentation into structured subdirectories
- Move README-zh.md to docs/i18n/README-zh.md
- Move development docs to docs/development/ (README-DEV.md, README-DEV-zh.md)
- Move user guides to docs/guides/ (CLI_USAGE.md, CURSOR_HELP.md, MCP_CLIENT_CONFIGURATORS.md)
- Move migration guides to docs/migrations/ (v5_MIGRATION.md, v6_NEW_UI_CHANGES.md, v8_NEW_NETWORKING_SETUP.md)
- Move reference docs to docs/reference/ (CUSTOM_TOOLS.md, TELEMETRY.md)
- Update all internal links in README
The pypa/gh-action-pypi-publish action does not support being called
from nested composite actions due to GitHub Actions context variable
limitations (github.action_repository not propagating correctly).
Inline the publish steps directly in release.yml to avoid the issue.
See: https://github.com/pypa/gh-action-pypi-publish/issues/338
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* Update the major tag of a version as well when publishing to Docker
Useful for the asset store releases
* feat: trigger publish workflows automatically after version bump and release creation
It should work in theory, and correctly release to Docker and pypi via tags.
* feat: consolidate release workflows into single pipeline with reusable actions
Refactored version bump, Docker publish, and PyPI publish workflows into a unified release pipeline that runs sequentially. Created reusable composite actions for Docker and PyPI publishing to eliminate duplication.
Changes:
- Rename bump-version.yml to release.yml with three jobs: bump, publish_docker, publish_pypi
- Create .github/actions/publish-docker/action.yml with configurable inputs for image, version, branch
Marcus Sanatan
Bryan Thompson
David Sarno