sft-versioning-guide

You determine patch, minor, or major version bumps by categorizing changes as content updates, new skills, or breaking changes. This process enforces consistent semantic versioning and prevents breaking plugin invocations during release workflows.

Updating a changelog using Keep a Changelog conventions involves structuring release notes with standardized categories for added, changed, and removed features. This process tracks version history and keeps CHANGELOG.md up to date during release workflows.

You need to declare compatibility in plugin.json during release workflows to clarify version requirements and prevent breaking changes. This step validates that the plugin manifest aligns with the applied semantic version bump before publication.

The best way to manage semantic versioning for skill-factory plugins is to automate version bump decisions and changelog updates during the release workflow. This provides a repeatable process for release planning, version validation, and compatibility declaration.

This versioning workflow integrates into Git release processes without requiring specific Git setup. It applies semantic versioning rules and changelog management to your plugin repository to track version history and validate compatibility.

You prevent breaking changes by enforcing semantic versioning rules and declaring compatibility in plugin.json. This validates version bumps and guards against breaking invocations before finalizing the release.