// Generate a commit message, commit all changes, run deploy_pip.ps1 to publish to PyPI, and tag HEAD with the deployed version on success
How to add i18n to all the ts files, and use the compile_i18n.cmd command to compile the ts files
Prefer the repository .venv Python interpreter for Python commands, tests, scripts, package tooling, and AI coding workflows when .venv exists.
Generate a commit message based on current changes and commit all staged and unstaged changes to git
| name | deploy |
| description | Generate a commit message, commit all changes, run deploy_pip.ps1 to publish to PyPI, and tag HEAD with the deployed version on success |
When instructed to deploy, release, or publish to PyPI, follow these steps in order:
// turbo
git status --short
If there are uncommitted changes:
git diff --stat and git diff to review them.
// turbogit diff --stat
// turbo
git diff
git add -A
// turbo
git commit -m "<generated commit message>"
If there are NO uncommitted changes, proceed directly to Step 2.
// turbo
.\.venv\Scripts\Activate.ps1; powershell -File ".\deploy_pip.ps1"
Wait for this to complete. If the command fails (non-zero exit code or error output), STOP here and report the error to the user. Do NOT tag.
The deploy script calls setup.py, which increments the version. The version is printed in the output from setup.py as:
latest_version is X.Y.Z new version is X.Y.W
Search for "new version is" in the terminal output to find the exact version number (e.g., 1.0.98).
// turbo
git tag v<version>
Replace <version> with the version obtained in step 3 (e.g. 1.0.97).
// turbo
git push
// turbo
git push --tags
Tell the user: