pf ver
To see what is installed on this machine instead (pf, plugins, skills, extensions), use pf versions (pf vs).
pf ver is major.minor versioning for a repo, including monorepos where every package has its own version and the whole stack has one too. It runs the bundled /ver CLI, and uses the newest copy of it that pf can find (see Skills).
pf ver # list versions, with ready-to-run bump commands
pf ver bump packages/pulpfixer minor
pf ver bump packages/kit packages/pulpfixer minor # several targets, the stack minor rises once
pf ver init # create versions.json, or add newly found packages
pf ver sync # rewrite manifests from versions.json
pf ver --dry-run # previewThe state lives in versions.json at the repo root. Never edit versions in manifests by hand: pf ver bump updates versions.json and each manifest together.
Rules of thumb
- Bump a package’s minor version when you change that package. Use major only for breaking changes.
- Bump a package only when its own files changed. A change in core that needs a new kit change bumps both.
- A published version can never be reused, so bump before you publish.
The coding agent can list and bump versions with the pf_versions and pf_bump tools. See Agent tools.
Last updated on