Skip to Content
DevelopmentVersioning and release

Versioning and release

Versioning

Every package and the whole stack have a major.minor version, kept in versions.json.

When you change a package, bump its minor version before you finish:

pnpm ver bump packages/pulpfixer minor pnpm ver bump packages/kit packages/pulpfixer minor # several targets; the stack minor rises once
  • Use major only for breaking changes.
  • Never edit versions in manifests by hand.
  • Bump a package only when its own files changed. A core change that depends on a new kit change bumps both.
  • After adding or removing a package, run pnpm ver init (--prune for removals).

The packages that get versions are packages/pulpfixer, packages/kit, packages/plugin-aws, packages/plugin-system, packages/plugin-yubikey, packages/preset-cursor, packages/preset-suite, packages/ext-bg-tone and packages/docs.

Release

pnpm release # typecheck, test, build, npm publish --dry-run for every unpublished package pnpm publish:cellars # the real publish

pnpm release is always a dry run. It publishes nothing, and it lists every package whose version the registry lacks, in dependency order (kit, plugins, extensions and presets, core). pnpm publish:cellars publishes without a confirmation prompt. A published version can never be reused, so bump first.

Core pins kit and the built-in plugins to exact versions, and users only update pulpfixer, so the release script refuses to publish a dependency without a new core. The exceptions are a preset (@pulpfixer/preset-*) and a suite extension (@pulpfixer/ext-*): pf sys apply and pf update fetch their latest version, so they are published alone and never drag core along. The extension’s .vsix is built by its prepack script (and by pnpm build), and the .vsix version is the package version.

packages/docs is private and is never published.

Never publish unless you were asked to.

The dev cycle

./pf cycle [--message m] [--no-push] [--yes] [--dry-run] in the checkout bumps changed packages (core goes along), commits, runs pnpm run publish:cellars, pushes with pf git push (the primary remote, then the backup remotes; --no-push skips it, and a failed push does not stop the update but makes the cycle exit 1), then runs pf u --yes so the global pf updates itself.

Last updated on