releasing-clickup-cli

Automating npm publish and Homebrew tap updates requires an end-to-end workflow that triggers publication, updates the tap, and syncs metadata. This coordinates cross-channel publication to reduce manual errors and speed up CLI release cycles.

Synchronizing release notes across npm and Homebrew involves automated version consistency checks and metadata synchronization during the release workflow. This ensures SKILL.md and documentation remain aligned with the published version across all distribution channels.

Yes, a single end-to-end workflow can bump versions and deploy to both npm and Homebrew. The process automates version tagging, triggers npm publish, updates the Homebrew tap, and verifies artifact consistency before deployment.

An automated CLI release workflow implements version consistency checks to verify alignment across npm, Homebrew, and agent skill metadata. These checks validate that version bumps synchronize correctly before cross-channel publication completes.

You need to sync agent skill metadata during a CLI release when bumping versions and publishing artifacts. This synchronization ensures local skill metadata stays aligned with the new version deployed to npm and updated in the Homebrew tap.