chore: bump version to 0.1.96

[CarmenDou]

Bump @insforge/cli from 0.1.95 to 0.1.96.

• package.json: 0.1.95 → 0.1.96
• package-lock.json: 0.1.95 → 0.1.96

🤖 Generated with Claude Code

---

Summary by cubic

Bump @insforge/cli to 0.1.96 for the next patch release. Updates package.json and package-lock.json to keep versions aligned; no code changes.

^{Written for commit 48e2362. Summary will update on new commits.}

Note

Bump package version to 0.1.96

Updates the version field in package.json from 0.1.95 to 0.1.96.

^{Macroscope summarized 48e2362.}

Summary by CodeRabbit

• Chores
  • Updated the app’s CLI package version to 0.1.96.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e8ab699e-1091-4e21-bf98-100afc8802eb

📥 Commits

Reviewing files that changed from the base of the PR and between 96aa4e3 and 48e2362.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json

---

Walkthrough

The version field in package.json for @insforge/cli is incremented from 0.1.95 to 0.1.96. No other files or fields are modified.

Version Bump

Layer / File(s)	Summary
Package version increment package.json	version field updated from 0.1.95 to 0.1.96.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• InsForge/CLI#113: Same pattern — single version bump in package.json.
• InsForge/CLI#183: Directly adjacent version bump (0.1.94 → 0.1.95).
• InsForge/CLI#147: Identical change structure, bumping @insforge/cli version in package.json.

Suggested reviewers

• jwfing

Poem

🐇 A tiny hop, a single line,
The version ticks from five to nine-
teen-six, the bunny stamps the ground,
0.1.96 is found!
Off to prod we bound! 🌿

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the version bump to 0.1.96.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-version-0.1.96

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Greptile Summary

This PR bumps the @insforge/cli package version from 0.1.95 to 0.1.96 in both package.json and package-lock.json. The change is mechanical and isolated to version fields only.

• package.json: version field updated from 0.1.95 to 0.1.96.
• package-lock.json: version updated in both the root metadata and the packages[""] entry, which is the correct and consistent way to reflect a version change in lockfile version 3.

Confidence Score: 5/5

Safe to merge — only the package version string is updated, with no logic or dependency changes.

Both package.json and package-lock.json are updated consistently and correctly. No source code, dependencies, scripts, or configuration fields were touched.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Version field bumped from 0.1.95 to 0.1.96; no other changes.
package-lock.json	Version updated in both root-level and packages[""] entries, consistent with the package.json bump.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: chore bump version] --> B[package.json\nversion: 0.1.95 → 0.1.96]
    A --> C[package-lock.json\nroot version: 0.1.95 → 0.1.96]
    C --> D[packages root entry\nversion: 0.1.95 → 0.1.96]
    B --> E{Versions consistent?}
    C --> E
    D --> E
    E -->|Yes| F[✅ Ready to publish\n@insforge/cli@0.1.96]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[PR: chore bump version] --> B[package.json\nversion: 0.1.95 → 0.1.96]
    A --> C[package-lock.json\nroot version: 0.1.95 → 0.1.96]
    C --> D[packages root entry\nversion: 0.1.95 → 0.1.96]
    B --> E{Versions consistent?}
    C --> E
    D --> E
    E -->|Yes| F[✅ Ready to publish\n@insforge/cli@0.1.96]

Loading

_{Reviews (1): Last reviewed commit: "chore: bump version to 0.1.96" | Re-trigger Greptile}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[jwfing]

LGTM - approved.