versioning

To prevent manual edits to plugin version fields, you need an automated release workflow that enforces version consistency. This Skill blocks direct version updates in plugin.json, SKILL.md, and marketplace.json, ensuring only the release pipeline can modify version fields.

Synchronizing version numbers across plugin.json, SKILL.md, and marketplace.json requires automated cross-file consistency checks. This Skill validates that all version locations stay aligned during the release pipeline, preventing mismatches between configuration files.

Automated version bumping is the process of incrementing plugin version numbers through a release pipeline rather than manual edits. You need it when managing multiple plugin and skill files to ensure consistent, traceable version updates across all repository locations.

Yes, this versioning workflow integrates directly with changelog and release scripts. It ensures the release pipeline updates version fields while simultaneously generating an audit-ready changelog that provides full traceability for all version updates and release notes.

No, you cannot manually update version fields when the automated release workflow is active. This Skill enforces guardrails that block manual edits to version fields in plugin.json, SKILL.md, and marketplace.json, requiring all version bumps to route through the release pipeline.

The best way to maintain version consistency across multiple plugin files is enforcing an automated release workflow with cross-file validation. This approach centralizes version control, prevents human error from manual edits, and guarantees synchronization across plugin.json, SKILL.md, and marketplace.json.