release
- Repo stars 6,503
- License Apache-2.0
- Author repo plano
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @katanemo · Apache-2.0
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
Prepare a release version bump. The user may provide the new version number as $ARGUMENTS (e.g., `/release 0.4.12`), or a bump type (`major`, `minor`, `patch`).
If no argument is provided, read the current version from `cli/planoai/__init__.py`, auto-increment the patch version (e.g., `0.4.11` → `0.4.12`), and confirm with the user before proceeding.
Update the version string in ALL of these files:
- `.github/workflows/ci.yml`
- `cli/planoai/__init__.py`
- `cli/planoai/consts.py`
- `cli/pyproject.toml`
- `build_filter_image.sh`
- `config/validate_plano_config.sh`
- `docs/source/conf.py`
- `docs/source/get_started/quickstart.rst`
- `docs/source/resources/deployment.rst`
- `apps/www/src/components/Hero.tsx`
- `demos/llm_routing/preference_based_routing/README.md`
Do NOT change version strings in `*.lock` files or `Cargo.lock`.
After updating all version strings, run `cd cli && uv lock` to update the lock file with the new version.
After making changes, show a summary of all files modified and the old → new version.
Sections and files
Listed in source order.
sections -> → → → → →
terms -> Prepare a release version bump. · Do NOT change version strings in .lock files or Cargo.lock. · After updating all version strings, run cd cli && uv lock to update the lock file with the new version. · After making changes, show a summary of all files modified and the old → new version.
files/cmd -> /release 0.4.12 · major · minor · patch · cli/planoai/__init__.py · 0.4.11 · 0.4.12 · .github/workflows/ci.yml
body sha256 -> 940321d58e6b
Prepare a release version bump. The user may provide the new version number as $ARGUMENTS (e.g.,
/release 0.4.12), or a bump type (major,minor,patch).If no argument is provided, read the current version from
cli/planoai/__init__.py, auto-increment the patch version (e.g.,0.4.11→0.4.12), and confirm with the user before proceeding.Update the version string in ALL of these files:
.github/workflows/ci.yml-cli/planoai/__init__.py-cli/planoai/consts.py-cli/pyproject.toml-build_filter_image.sh-config/validate_plano_config.sh-docs/source/conf.py-docs/source/get_started/quickstart.rst-docs/source/resources/deployment.rst-apps/www/src/components/Hero.tsx-demos/llm_routing/preference_based_routing/README.mdDo NOT change version strings in
*.lockfiles orCargo.lock.