Release pipeline unblocked after tag collision bug
Release automation is fixed after months of failed publish attempts that produced phantom versions never actually published to npm.
Release automation was broken. Five consecutive attempts (PRs #27 through #31) failed to publish @gitpulse/cli to npm — each produced a version bump but no actual release. The root cause: two packages shared one tag namespace, and release-please would pick the highest version's tag for both, creating collisions whenever versions diverged. Now only the CLI is managed. One package, one tag, one release cycle. The pipeline should finally work.
The fix also rolls back a phantom version. cli/package.json had been bumped to 0.1.2 by those failed attempts — a version that never existed on npm, never got a git tag. That gets reverted to 0.1.1, the last version actually published.
In the release workflow, output handling was simplified and made defensive. Since the root package is no longer in the config, the action might emit either bare outputs (release_created, tag_name, major) or path-scoped ones (cli--release_created, etc). The workflow now coalesces both forms so downstream jobs don't break either way.