chore(main): release 0.1.4

[github-actions]

🤖 I have created a release beep boop

0.1.4 (2026-05-04)

Features

• dogfood published @gitpulse/cli; add Vercel config; package README (#35) (2de061b)

Bug Fixes

• release-please: drop root from managed packages; reset cli to 0.1.1 (#33) (3953a36)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Automated release PR generated by Release Please, bumping @gitpulse/cli from 0.1.3 to 0.1.4. The changes include a version bump in cli/package.json, a corresponding update to .release-please-manifest.json, and a new CHANGELOG.md entry covering two merged PRs (dogfood/Vercel config feature and a release-please fix).

Confidence Score: 5/5

This PR is safe to merge — it is a fully automated release-please version bump with no logic changes.

All three changed files are standard release-please outputs: a manifest version bump, a package.json version bump, and a CHANGELOG prepend. No code logic, dependencies, or configuration were altered.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 0.1.3 to 0.1.4 for the cli package — expected release-please output.
cli/CHANGELOG.md	New 0.1.4 section prepended with two entries (features + bug fixes) matching the merged PRs.
cli/package.json	Package version bumped from 0.1.3 to 0.1.4 — no other fields changed.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] -->|Reads merged PRs| B[Generate release PR]
    B --> C[Bump .release-please-manifest.json\ncli: 0.1.3 → 0.1.4]
    B --> D[Bump cli/package.json\nversion: 0.1.3 → 0.1.4]
    B --> E[Prepend cli/CHANGELOG.md\nwith 0.1.4 entry]
    C & D & E --> F[Merge PR #38]
    F --> G[Tag v0.1.4 & Publish\n@gitpulse/cli@0.1.4]

Loading

_{Reviews (1): Last reviewed commit: "chore(main): release 0.1.4" | Re-trigger Greptile}

[github-actions]

🤖 Created releases:

• v0.1.4

🌻