bump to version 0.1.74

[tonychang04]

Ship #119 (install better-auth/skills when --auth better-auth is used).

The CLI already installed insforge/agent-skills and find-skills globally on every link/create; 0.1.74 also installs the upstream better-auth/skills pack whenever the user opts into Better Auth, so agents get the provider's own scaffolding patterns alongside InsForge's bridge skills.

Merge order:

1. feat(skills): install better-auth/skills when --auth better-auth #119 (feature)
2. This PR (bump)
3. Tag v0.1.74 on main → GitHub Actions publishes to npm

🤖 Generated with Claude Code

---

Summary by cubic

Release 0.1.74 of @insforge/cli, enabling auto-install of better-auth/skills when --auth better-auth is used. This ships Better Auth scaffolding alongside insforge/agent-skills and find-skills.

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

Summary by CodeRabbit

• Chores
  • Incremented package version to 0.1.74.

[coderabbitai]

Walkthrough

The package version in package.json is incremented from 0.1.73 to 0.1.74. No dependencies, scripts, or other configuration changes.

Changes

Package Version Bump

Layer / File(s)	Summary
Version increment package.json	The version field is bumped from 0.1.73 to 0.1.74.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• InsForge/CLI#113: Both PRs update only the package.json version field with an identical change pattern.

Suggested reviewers

• jwfing

Poem

🐰 A hop, a skip, a version bump—
From .73 to .74, the numbers jump!
No code disturbed, just one small change,
A minor increment, tidy and strange.
Rabbit approves of this orderly patch! 🥕

🚥 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 to version 0.1.74' directly and accurately describes the sole change in the pull request, which is incrementing the package version from 0.1.73 to 0.1.74.
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 bump-version-0.1.74

---

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

[jwfing]

LGTM, approved.

[jwfing]

LGTM, approved.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 3: The version field "version": "0.1.74" was bumped before PR `#119` is
merged which would publish v0.1.74 missing the better-auth change; revert or
remove this version bump in package.json (the "version" entry) so the PR doesn't
advance the package version, then reapply or update the version after PR `#119`
("feat(skills): install better-auth/skills when --auth better-auth") is merged
to ensure the published release includes that feature.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 301f8596-1097-420d-b295-adbcb1e7b0f5

📥 Commits

Reviewing files that changed from the base of the PR and between 6f50f31 and d60ef5c.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Check if PR `#119` is merged before this version bump PR is merged.

# Check PR `#119` status
echo "=== Checking status of PR `#119` ==="
gh pr view 119 --json number,title,state,mergedAt,baseRefName,headRefName

# Check if PR `#119` commits are in the target branch (main)
echo -e "\n=== Checking if PR `#119` changes are in main branch ==="
gh pr view 119 --json commits --jq '.commits[].oid' | head -5 | while read commit; do
  echo "Checking commit $commit in main:"
  git branch -r --contains "$commit" 2>/dev/null | grep "origin/main" && echo "✓ Found in main" || echo "✗ Not in main"
done

Repository: InsForge/CLI

Length of output: 417

---

This PR cannot be merged until PR #119 has been merged first.

PR #119 ("feat(skills): install better-auth/skills when --auth better-auth") is currently in OPEN state and has not been merged into main. According to the stated merge order, PR #119 must be merged before this version bump is applied. Merging this version bump before PR #119 will result in v0.1.74 being published without the better-auth feature included.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 3, The version field "version": "0.1.74" was bumped
before PR `#119` is merged which would publish v0.1.74 missing the better-auth
change; revert or remove this version bump in package.json (the "version" entry)
so the PR doesn't advance the package version, then reapply or update the
version after PR `#119` ("feat(skills): install better-auth/skills when --auth
better-auth") is merged to ensure the published release includes that feature.

[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}