release-plugin

Automate plugin release packaging by reading release-mapping.yaml to copy mapped skill directories into per-plugin release folders. This process preserves the required structure and copies supporting files to ensure all components are present for a consistent release.

Version bumping updates the version field in .claude-plugin/plugin.json and marketplace metadata according to patch, minor, or major increments. This ensures your plugin release metadata accurately reflects the scope of changes during the automated packaging process.

Release-mapping.yaml defines the target plugin packaging mappings located at the repository root. It dictates which skill directories and supporting files are copied into specific plugins/<plugin>/ directories to structure the release correctly.

Validate plugin release integrity by verifying that source mappings exist and destination directories are successfully created. The automated packaging process concludes by checking these conditions and reporting a packaged release summary.

No, automated plugin packaging requires a release-mapping.yaml file at the repository root. Without this mapping configuration, the process cannot determine which source files to copy or where to structure the per-plugin release directories.

Manage multiple plugin releases by using an automated workflow that reads a central mapping file to package source files into individual plugin directories. This approach applies version bumps and validates each destination separately to ensure release consistency.