Releasing heptabase-cli-skills

This repo ships a public plugin package installed via the Claude Code marketplace, Cursor, npx skills, and OpenCode. Claude Code caches installed plugins by resolved plugin version, so users only receive updates when the version changes — pushing commits without a bump ships nothing.

Conventions (and why)

• .claude-plugin/plugin.json version is the single source of truth. Claude Code resolves the version as: plugin.json → marketplace.json plugin entry → commit SHA. Never add a version to a marketplace.json plugin entry — it would silently shadow future strategy changes.
• .cursor-plugin/plugin.json must mirror the same version on every release (Cursor reads its version from that file).
• Tag format: vX.Y.Z matching the manifest version.
• GitHub release title: Compatible with CLI v<range>, where <range> is metadata.heptabase-cli-version-range from skills/heptabase-cli/SKILL.md (e.g. 0.4.x → "Compatible with CLI v0.4.x"). The title states compatibility, not features, and stays identical across releases in the same CLI range.
• Release notes are auto-generated from merged PR titles (--generate-notes). There is no CHANGELOG file. This means changes should land via PRs with clear conventional-commit titles (feat: ..., fix: ...) — the PR title is the changelog entry.

Version bump rules