Version Release Skill

Apply Semantic Versioning across CCAM:

• Patch (X.Y.Z+1): backward-compatible fixes, docs-only work, dependency/security maintenance, refactors, or small improvements without a substantial new capability.
• Minor (X.Y+1.0): backward-compatible features or meaningfully larger capabilities such as new workflows, pages, integrations, API fields/routes, or major UX surfaces.
• Major (X+1.0.0): breaking public behavior, removed or renamed contracts, required migrations, or fundamental product/architecture changes.

Choose the highest applicable category. If the boundary is ambiguous, prefer the higher bump or ask before release. Do not classify from diff size or commit count alone. An explicit user-requested version takes precedence over automatic classification. Record the override, synchronize that exact version, and do not silently substitute a different patch, minor, or major number.

Automated release preparation

Use the manual Prepare Release Bump workflow for routine releases. Its repository-specific input names are intentionally different from standard SemVer labels:

• major increments the first component: X.Y.Z to X+1.0.0.
• intermediate increments the standard SemVer minor component: X.Y.Z to X.Y+1.0.
• minor increments the standard SemVer patch component: X.Y.Z to X.Y.Z+1.

Preview the exact plan locally without writes:

node scripts/bump-release.js intermediate --dry-run --json