chore(main): release 0.1.5

[github-actions]

🤖 I have created a release beep boop

0.1.5 (2026-05-07)

Features

• add .gitpulse.json config file for publication title and subtitle (#41) (81c302d)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

Automated release PR generated by Release Please, bumping the @gitpulse/cli package from 0.1.4 to 0.1.5 to publish the .gitpulse.json config file feature landed in #41.

• cli/package.json: Version field updated from "0.1.4" to "0.1.5".
• cli/CHANGELOG.md: New 0.1.5 entry added documenting the .gitpulse.json config file feature.
• .release-please-manifest.json: Manifest version tracking updated to "0.1.5".

Confidence Score: 5/5

Safe to merge — all three changes are version bookkeeping generated by Release Please with no logic changes.

The entire diff is version metadata: one JSON manifest, one package.json field, and one CHANGELOG entry — all consistent with each other at 0.1.5 and aligned with the feature commit they reference.

No files require special attention.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from "0.1.4" to "0.1.5" by Release Please automation — no issues.
cli/CHANGELOG.md	New 0.1.5 changelog entry added describing the .gitpulse.json config file feature — no issues.
cli/package.json	Package version bumped from "0.1.4" to "0.1.5" — no issues.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Release Please Bot] -->|detects feat commit in #41| B[Creates release PR #42]
    B --> C[Bumps .release-please-manifest.json\n0.1.4 → 0.1.5]
    B --> D[Bumps cli/package.json\n0.1.4 → 0.1.5]
    B --> E[Appends cli/CHANGELOG.md\n0.1.5 entry]
    C & D & E --> F[PR merged to main]
    F --> G[GitHub Actions publishes\n@gitpulse/cli@0.1.5 to npm]

Loading

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

[github-actions]

🤖 Created releases:

• v0.1.5

🌻