GitPulse's release pipeline is back online after five consecutive failures. The culprit: release-please was managing two packages and colliding on git tags whenever versions diverged. The root package — never published to npm, never useful to anyone downstream — has been dropped from release configuration entirely. Only @gitpulse/cli now ships to users, eliminating the version drift that broke every release attempt since PR #27.
Help text and reality are now in agreement. The --help output has been corrected to match what GitPulse actually does, and a problematic plugin has been removed, reducing the surface area for future breakage.
Release-please was managing two packages and colliding on git tags whenever versions diverged — five PRs failed to publish. The root package is private, never published to npm, and shouldn't have been in the release pipeline at all.
GitPulse 0.1.2 drops a problematic plugin and fixes documentation alignment to get the automated release workflow moving again.