qalma-release

Qalma Release

@qalma/editor, @qalma/skills, and @qalma/kit are published to npm under the latest dist-tag while the public API stabilizes. The packages are pre-1.0, but public releases use normal semver versions without prerelease suffixes. The scripted release path bumps the minor version on every release (0.2.0, 0.3.0, and so on).

Releases are tag-driven: a vX.Y.Z git tag pushed to main triggers GitHub Actions, which builds, re-derives the version from the tag, and publishes all three packages via npm's OIDC Trusted Publisher (no npm token in CI).

For the full architecture, history, and troubleshooting, read release-pipeline.md.

Cut a Release

1. Make sure main is clean and up to date (git status, git pull).

2. If the current version is still on the historical beta line, bootstrap the first normal semver release explicitly:

   pnpm nx release 0.2.0 --skip-publish --dry-run
   pnpm nx release 0.2.0 --skip-publish
   node tools/sync-changelog-doc.mjs
   

   This one explicit version is needed because Nx's native minor bump from 0.1.0-beta.4 resolves to 0.1.0, while Qalma's new policy is to move to the next minor without a suffix.

3. After 0.2.0, preview the next minor bump with pnpm release:dry-run.

4. After 0.2.0, run the normal release command with pnpm release.

   For an explicit one-off version, call Nx directly so the version argument is passed before the changelog-sync command:

   pnpm nx release <version> --skip-publish
   node tools/sync-changelog-doc.mjs
   

   These scripts or commands run nx release ... --skip-publish, then sync the generated editor changelog into the docs changelog. The release portion:

   • Runs the preVersionCommand (./node_modules/.bin/nx run-many -t build -p editor skills ui-kit).
   • Writes the new version into libs/editor/package.json and dist/libs/editor/package.json, libs/skills/package.json and dist/libs/skills/package.json, plus libs/ui-kit/package.json and dist/libs/ui-kit/package.json.
   • Generates project changelogs from conventional commits.
   • Commits the manifest and changelog change as chore(release): publish <version>.
   • Creates an annotated tag v<version> on that commit.
   • Skips publishing (CI does that).