Command: /version-update or simply ask Claude to "update versions"
This command will:
-
Check plugin changes since last release:
- Find the last release commit (search for "release" in commit messages)
- Check git history for each plugin since last release
- Identify plugins that have changes but haven't had version bumps
-
Update plugin versions:
- For each changed plugin, determine version increment based on change type:
- Patch version (0.3.4 → 0.3.5): Bug fixes, eslint fixes, small improvements
- Minor version (0.3.4 → 0.4.0): New features, API changes, significant enhancements
- Add changelog entries describing the changes with appropriate detail level
- For each changed plugin, determine version increment based on change type:
-
Update core version:
- Check
core/directory changes since last release - Increment minor version in
core/total-conversion-build.js(e.g., 0.40.0 → 0.41.0) - Add changelog entries for core improvements
- Focus on user-visible changes and bug fixes
- Check
-
Update mobile app version:
- Update
versionNameinmobile/app/build.gradleto match core version - Change from
versionName "0.40.0"toversionName "0.41.0"
- Update
git log --oneline [last-release-commit]..HEAD -- plugins/[plugin-name].js- Check if version in plugin header needs updating
- Add concise changelog entries (like "Fix portal snap positioning bug")
git log --oneline [last-release-commit]..HEAD -- core/- Update core version and changelog
- Exclude translation commits and mobile-specific changes from core changelog
- Plugin:
'Fix portal snap positioning bug' - Core:
'Fix RegionScore tooltip HTML rendering','Update MODs display colors'
Keep descriptions concise and user-focused, avoiding technical implementation details.