plugin-maintenance

To synchronize version bumps for a plugin release, you must update the version fields in both plugin.json and marketplace.json simultaneously. This prevents mismatched releases and ensures the marketplace reflects the correct plugin version.

Ensuring bash hook scripts are compatible with macOS Bash 3.2 requires avoiding forbidden Bash 4+ features and using prescribed Bash 3.2-compatible alternatives. You should run specific syntax checks to verify compatibility before publishing.

Testing and releasing a plugin update locally involves following a reproducible checklist: running syntax tests on hook scripts, loading the plugin locally to verify behavior, and checking cross-package documentation synchronization before publishing the update.

Plugin updates cause version mismatches in the marketplace when plugin.json and marketplace.json are not updated together. Synchronizing version fields across both files during every release prevents this issue and ensures users receive safe upgrades.

You need to update cross-package documentation for plugin skills when modifying skill documentation or releasing new plugin versions. This synchronization across plugin and standalone skill directories prevents outdated information from reaching users after an update.