chore: bump CLI version to 0.1.79

[tonychang04]

Version bump after #127 (auth verification + password policy in insforge.toml) lands on main. Triggers npm publish on release.

🤖 Generated with Claude Code

---

Summary by cubic

Bump @insforge/cli to 0.1.79 to release auth verification and insforge.toml password policy support. This triggers npm publish on release.

^{Written for commit 4fbd306. Summary will update on new commits.}

Note

Bump CLI version to 0.1.79

Updates the version field in package.json from 0.1.78 to 0.1.79.

^{Macroscope summarized 4fbd306.}

Summary by CodeRabbit

• Chores
  • Version bump to 0.1.79

[coderabbitai]

Walkthrough

The package version in package.json was incremented from 0.1.78 to 0.1.79. No other package configuration, dependencies, scripts, or metadata were modified.

Changes

Package Version Increment

Layer / File(s)	Summary
Version field increment package.json	The version field was bumped from 0.1.78 to 0.1.79.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• InsForge/CLI#118: Both PRs bump the version field in package.json with no other code-level changes.
• InsForge/CLI#113: Both PRs increment package.json's version field by a patch release with no other modifications.
• InsForge/CLI#121: Both PRs bump package.json's version field without any other code or config changes.

Suggested reviewers

• jwfing

Poem

🐰 A number ticks upward, small and bright,
From seventy-eight to seventy-nine in flight,
A patch release, a bump so neat,
Makes the version dance complete! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: a version bump from 0.1.78 to 0.1.79 in package.json, which is the only modification in this pull request.
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 chore/bump-version-0.1.79

---

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

[greptile-apps]

Greptile Summary

Bumps the @insforge/cli package version from 0.1.78 to 0.1.79 in package.json and the matching entries in package-lock.json, intended to trigger an npm publish after the auth-verification and password-policy changes land on main.

• package.json: single version field updated to 0.1.79.
• package-lock.json: both the root-level version and the packages[""].version entry updated consistently to 0.1.79; no dependency changes.

Confidence Score: 5/5

Safe to merge — only the version string is updated, both files are consistent, and no logic or dependencies are touched.

The change is a two-file version-string update: package.json and both version entries in package-lock.json move from 0.1.78 to 0.1.79. No source code, dependencies, scripts, or configuration change. The lockfile is internally consistent with the manifest.

No files require special attention.

Important Files Changed

Filename	Overview
package.json	Version field bumped from 0.1.78 to 0.1.79; no other changes.
package-lock.json	Version field updated in both the root and the packages[""] entry to match package.json; lockfile is consistent.

Sequence Diagram

sequenceDiagram
    participant PR as This PR (v0.1.79)
    participant Main as main branch
    participant CI as CI / Release Workflow
    participant npm as npm Registry

    PR->>Main: Merge version bump
    Main->>CI: Trigger release workflow
    CI->>CI: "Build & test"
    CI->>npm: "Publish @insforge/cli@0.1.79"

Loading

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

[cubic-dev-ai]

No issues found across 2 files

_{Tip: cubic could auto-approve low-risk PRs like this, if it thinks it's safe to merge. Learn more}

[jwfing]

LGTM, approved.