prepare-release

Automate changelog and version updates by inspecting changed plugins against origin/main, then synchronizing version fields in marketplace.json and plugin.json while inserting new changelog entries. This ensures consistent versioning and documentation across multi-plugin repositories during publish cycles.

The best way to synchronize documentation is to automatically update plugin README sections and insert changelog entries based on modified files. This process preserves unmodified plugins and maintains integrity between public documentation and actual version numbers.

Yes, you can reset plugin version numbers in marketplace.json while preserving unmodified plugins. The process loads and validates marketplace and plugin metadata, applying version bumps and documentation updates exclusively to modified plugins to maintain repository integrity.

Prepare a multi-plugin marketplace release by automating version consistency checks and compliance validation. The workflow identifies changed plugins, updates version fields across metadata files, and validates generated changelog information to prevent release risks from manual preparation errors.

Automated release preparation works specifically for multi-plugin repositories during publish cycles. It handles loading and validating marketplace metadata, updating version fields, and inserting changelog entries to ensure consistent versioning and documentation updates across all modified plugins.

Manual release preparation leads to inconsistencies because version resetting, changelog compilation, and documentation synchronization involve multiple files. Automating these tasks enforces consistent versioning, updates metadata fields uniformly, and performs integrity checks to avoid missing version bumps or outdated docs.