Skip to content

bump CLI version to 0.1.80#130

Merged
CarmenDou merged 1 commit into
mainfrom
chore/bump-version-0.1.80
May 15, 2026
Merged

bump CLI version to 0.1.80#130
CarmenDou merged 1 commit into
mainfrom
chore/bump-version-0.1.80

Conversation

@CarmenDou
Copy link
Copy Markdown
Contributor

@CarmenDou CarmenDou commented May 15, 2026

Summary by cubic

Bump @insforge/cli to 0.1.80 for the next release. Updates the version fields in package.json and package-lock.json.

Written for commit 155d57e. Summary will update on new commits. Review in cubic

Note

Bump CLI version to 0.1.80

Updates the version field in package.json from 0.1.79 to 0.1.80 and updates the lockfile accordingly.

Macroscope summarized 155d57e.

Summary by CodeRabbit

  • Chores
    • Patch version update (0.1.80)

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 15, 2026

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: ae3960c9-a6c8-4b20-921c-88b765d1dc69

📥 Commits

Reviewing files that changed from the base of the PR and between 82dac53 and 155d57e.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Walkthrough

This PR bumps the npm package version in package.json from 0.1.79 to 0.1.80. No other package metadata, dependencies, scripts, or configuration entries are modified.

Changes

Version Bump

Layer / File(s) Summary
Package version update
package.json
The version field is incremented from 0.1.79 to 0.1.80.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • InsForge/CLI#128: Bumps package.json version from 0.1.78 to 0.1.79, a sequential version release in the same manifest field.
  • InsForge/CLI#113: Bumps package.json version with no other code changes, matching the pattern of manifest-only version updates.

Suggested reviewers

  • jwfing

Poem

🐰 A digit dances, a number blooms,
From point-one-seventy-nine, new rooms,
To eighty now, the version grows,
The tiny hop that always flows.

🚥 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 'bump CLI version to 0.1.80' directly and clearly summarizes the main change: a version bump in package.json from 0.1.79 to 0.1.80.
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.

✏️ 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.80

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

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

@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented May 15, 2026

Greptile Summary

Bumps the @insforge/cli package version from 0.1.79 to 0.1.80 in both package.json and package-lock.json. No dependency changes, code changes, or configuration changes are included.

  • package.json: single version field updated to \"0.1.80\".
  • package-lock.json: both the root version field and the packages[\"\"].version field updated to \"0.1.80\", keeping the lock file consistent.

Confidence Score: 5/5

Safe to merge — only the package version string is changed, with no functional code or dependency modifications.

Both changed files update only the version field from 0.1.79 to 0.1.80, and the package-lock.json is consistent with package.json. There are no dependency additions, removals, or upgrades, and no source code is touched.

No files require special attention.

Important Files Changed

Filename Overview
package.json Version bumped from 0.1.79 to 0.1.80; no other changes.
package-lock.json Lock file version entries updated in sync with package.json (root and packages[""] both bumped to 0.1.80); no dependency changes.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[package.json\nversion: 0.1.79] -->|bump| B[package.json\nversion: 0.1.80]
    C[package-lock.json\nroot version: 0.1.79\npackages version: 0.1.79] -->|bump| D[package-lock.json\nroot version: 0.1.80\npackages version: 0.1.80]
Loading

Reviews (1): Last reviewed commit: "bump CLI version to 0.1.80" | Re-trigger Greptile

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Re-trigger cubic

Copy link
Copy Markdown
Member

@jwfing jwfing left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, approved.

@CarmenDou CarmenDou merged commit 5cc4c0e into main May 15, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants