chore: bump version to 0.1.84

[CarmenDou]

Summary by cubic

Bump @insforge/cli to version 0.1.84 for the next release. Updates package.json and package-lock.json to the same version.

^{Written for commit 83179dd. Summary will update on new commits. Review in cubic}

Note

Bump version to 0.1.84

Updates the version field in package.json from 0.1.83 to 0.1.84.

^{Macroscope summarized 83179dd.}

[coderabbitai]

Warning

Review limit reached

@CarmenDou, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 13 minutes and 28 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a6bc72af-a79c-4a73-852d-116cc006e4f8

📥 Commits

Reviewing files that changed from the base of the PR and between ca9d1eb and 83179dd.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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 and usage tips.}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[greptile-apps]

Greptile Summary

This PR bumps the package version to 0.1.84 in both package.json and package-lock.json. It also implicitly resolves a pre-existing version mismatch where package.json was at 0.1.83 while package-lock.json was still at 0.1.82.

• package.json is updated from 0.1.83 → 0.1.84.
• package-lock.json is updated from 0.1.82 → 0.1.84, skipping 0.1.83, which indicates the lock file was not regenerated during the previous version bump.

Confidence Score: 4/5

Safe to merge — both version files are now consistently at 0.1.84 and no functional code is changed.

The only change is a version bump. The lock file was previously one version behind package.json, meaning a past bump left the two files out of sync; this PR resolves that, though 0.1.83 is permanently absent from the lock file's history.

package-lock.json — it jumped directly from 0.1.82 to 0.1.84, indicating the lock file was not regenerated during the 0.1.83 bump.

Important Files Changed

Filename	Overview
package.json	Version bumped from 0.1.83 to 0.1.84 — straightforward, no other changes.
package-lock.json	Version bumped from 0.1.82 to 0.1.84, skipping 0.1.83 — indicates the lock file was previously out of sync with package.json.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[package.json v0.1.83] -->|bumped| B[package.json v0.1.84]
    C[package-lock.json v0.1.82] -->|was out of sync| D[package-lock.json v0.1.83 - missing]
    D -.->|skipped| E[package-lock.json v0.1.84]
    B & E --> F[Both files now in sync at v0.1.84]

Loading

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

[greptile-apps]

Lock file skipped a version — Before this PR, package.json was at 0.1.83 while package-lock.json was at 0.1.82, meaning the two files were out of sync. This PR fixes the inconsistency by bringing both to 0.1.84, but it means package-lock.json never recorded version 0.1.83. This suggests a prior version bump only edited package.json without running npm install (or equivalent) to regenerate the lock file. Going forward, make sure to regenerate package-lock.json after every version bump to keep them in sync.

[jwfing]

LGTM, approved.