publish-kibob

Automate Rust crate publishing and Homebrew formula updates by orchestrating version bumps, Git tagging, changelog updates, and tap maintenance in a single workflow. This ensures predictable, repeatable releases across CI and local environments.

Managing a release workflow that updates Cargo.toml and CHANGELOG.md requires enforcing a clean working tree, validating target versions, publishing crates, pushing Git tags, and refreshing the Homebrew formula checksum for consistency.

Yes, running a crates.io release process inside a CI pipeline is fully supported. The workflow validates credentials, ensures a clean working tree, and automates crate publishing, Git tagging, and Homebrew tap updates for repeatable CI releases.

Yes, the Homebrew formula update automatically refreshes the checksum after publishing. The workflow publishes crates to crates.io, pushes Git tags, and then updates the Homebrew tap formula with the correct checksum.

A release workflow requires a clean Git working tree before bumping versions to prevent uncommitted changes from corrupting the release. Enforcing this guardrail validates inputs and ensures predictable Cargo.toml and CHANGELOG.md updates.

Limitations when automating Homebrew tap maintenance and crate publishing together include the strict requirement for a clean working tree and valid credentials. The workflow halts if pre-release validation of target versions or post-release verification fails.