chore: bump version to 0.1.86

[Fermionic-Lyu]

Summary

• Bump CLI version to 0.1.86 so npm can be republished through the GitHub release workflow.
• Replaces the manually published 0.1.85 artifact that was built without the PostHog API key injection.

Verification

• npm test -- --run
• npm run lint
• POSTHOG_API_KEY=phc_local_sanity npm run build

---

Summary by cubic

Bump @insforge/cli to 0.1.86 to republish via the GitHub release workflow and replace the 0.1.85 artifact built without PostHog API key injection. Ensures the npm package is published with the correct build configuration.

^{Written for commit 2fce4d9. Summary will update on new commits.}

Review in cubic

Note

Bump version to 0.1.86

Updates the version field in package.json from 0.1.85 to 0.1.86.

^{Macroscope summarized 2fce4d9.}

Summary by CodeRabbit

• Chores
  • Updated package version to 0.1.86

[coderabbitai]

Walkthrough

The package.json version field for @insforge/cli is incremented from 0.1.85 to 0.1.86. No dependencies, scripts, entry points, or other metadata were modified.

Changes

Version Bump

Layer / File(s)	Summary
Version field update package.json	Package version incremented from 0.1.85 to 0.1.86.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• InsForge/CLI#114: Both PRs are simple package.json version bumps for @insforge/cli with no other code changes.
• InsForge/CLI#128: Both PRs only bump the @insforge/cli version in package.json with no other code changes.
• InsForge/CLI#138: Both PRs only bump the @insforge/cli version in package.json with no other code changes.

Suggested reviewers

• jwfing

Poem

🐰✨
A version bump, so small and neat,
From point-eighty-five, complete!
Now eighty-six takes up the throne,
The package grows, just one line shown! 📦

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and directly summarizes the main change: bumping the package version from 0.1.85 to 0.1.86.
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/release-0.1.86

---

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

[greptile-apps]

Greptile Summary

This PR bumps the @insforge/cli package version from 0.1.85 to 0.1.86 in both package.json and package-lock.json, with no functional code changes. The bump is intended to allow republishing via the GitHub release workflow after the prior 0.1.85 artifact was manually published without PostHog API key injection.

• Version updated from 0.1.85 → 0.1.86 in package.json and package-lock.json.
• No dependency changes, logic changes, or configuration changes are included.

Confidence Score: 5/5

Safe to merge — only the version string changes in both manifest files, with no functional code, dependency, or configuration modifications.

The diff is a two-file, two-field version bump with no logic, dependency, or build-script changes. The only risk would be a version number typo or mismatched values between the two files, both of which are correct here.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Version field bumped from 0.1.85 to 0.1.86; no other changes.
package-lock.json	Version field updated in both the root and the packages[""] entry to match package.json bump; no dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: bump version 0.1.85 → 0.1.86] --> B[package.json]
    A --> C[package-lock.json]
    B --> D[Triggers GitHub Release Workflow]
    C --> D
    D --> E[Build with POSTHOG_API_KEY injected]
    E --> F[Publish @insforge/cli@0.1.86 to npm]

Loading

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

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[jwfing]

LGTM, approved.