Versions & Release Policy

Current version

The latest stable release is always published to npm under the latest tag:

npm install -g @prokodo/cli@latest

Check which version you have installed:

prokodo --version

@prokodo/cli follows Semantic Versioning:

Increment	When
patch `0.x.Y`	Bug fixes, documentation updates, CI/infra changes
minor `0.X.0`	New commands or flags that are backwards-compatible
major `X.0.0`	Breaking changes to command signatures or config format

Releases are fully automated via GitHub Actions:

A maintainer triggers the Bump version workflow from the Actions tab and selects patch, minor, or major.
The workflow increments package.json, prepends a new section to the Changelog, commits the change, and pushes a vX.Y.Z git tag.
The Release workflow detects the new tag, runs the full test suite, and publishes to npm with pnpm publish.
The docs are rebuilt and deployed automatically.

# Install a specific version globally
npm install -g @prokodo/cli@0.1.0

# Or with pnpm
pnpm add -g @prokodo/cli@0.1.0

npm view @prokodo/cli versions --json

Or browse directly on npmjs.com.

# npm
npm update -g @prokodo/cli

# pnpm
pnpm update -g @prokodo/cli

After upgrading, run prokodo doctor to verify the new version is active and the environment is healthy.

Breaking changes

Any breaking changes are clearly marked in the Changelog and the major version is bumped. Check the changelog before upgrading across major versions.

CLI version	Node.js
0.x	≥ 18.0.0