chore: release v2.2.1

[carlos-alm]

Automated version bump to 2.2.1 and DEPENDENCIES.json update from publish workflow.

Merges the version bump commit from the release/v2.2.1 branch back into main.

[carlos-alm]

Release Notes — v2.2.1

Patch: Default model requires auth

Bug Fixes

• embedder: change default embedding model from jina-code to nomic-v1.5 (f40bb91)
• config: update config default and test to match nomic-v1.5 change (3a88b4c)
• ci: run benchmark after publish to prevent workflow cancellation (68e274e)
• ci: skip dev publish when merging release version bump PR (ceb4c9a)

Details

• jina-code is gated on HuggingFace and crashes without HF_TOKEN, making codegraph embed fail out-of-the-box
• nomic-v1.5 is public, same 768d dimensions, improved quality, 8192 token context
• Updated config defaults and test expectations to match
• Fixed publish workflow to skip dev publish when merging release version bump PRs
• Fixed benchmark workflow ordering to prevent publish workflow cancellation

[claude]

Claude finished @carlos-alm's task —— View job

---

PR Review: Release v2.2.1

Reviewing this release PR following the 4-phase review process for codegraph.

Todo List

• Phase 1: Root cause analysis
• Phase 2: Configuration change detection
• Phase 3: Test integrity check
• Phase 4: Code quality assessment
• Final rating and recommendation

Root Cause Analysis

Problem Being Solved: The default embedding model jina-code was gated on HuggingFace and required authentication (HF_TOKEN), causing codegraph embed to fail out-of-the-box for users without credentials.

Why This Approach: Switching to nomic-v1.5 as default is technically sound because:

• nomic-v1.5 is publicly accessible (no authentication required)
• Same dimensionality (768d) as jina-code
• Improved quality and larger context window (8192 tokens)
• Maintains compatibility while fixing user experience issue

Risk Assessment: ⚠️ MEDIUM - This is a legitimate bug fix addressing a real user-facing issue, not configuration relaxation.

Phase 2: Configuration Change Detection

✅ PASSED - The changes are appropriate:

• Updated default embedding model from jina-code to nomic-v1.5 in src/embedder.js:58 and src/config.js:22
• Updated corresponding test expectations in tests/unit/config.test.js:58
• Updated CLI help text and documentation to reflect the new default
• No linting rules relaxed, no test coverage thresholds lowered
• No build configuration changes

Phase 3: Test Integrity

✅ PASSED - Test changes are legitimate:

• Only one test modified: config default test updated from jina-code to nomic-v1.5
• This is a proper test update reflecting the intentional behavior change, not test weakening
• Test maintains same level of strictness, just validating the new expected default value
• No assertions removed or made less strict

Phase 4: Code Quality

✅ PASSED - This is a clean release PR:

• Automated version bump from release workflow (as expected)
• Standard changes: package.json, package-lock.json, DEPENDENCIES.json updates
• Native addon version synchronization updated correctly (2.1.0 → 2.2.1)
• Platform-specific dependencies properly versioned
• No manual code changes in this specific commit (all fixes were in previous commits)

Technical Assessment

The underlying fix addresses a real authentication barrier:

• Before: jina-code required HF_TOKEN, crashed without credentials
• After: nomic-v1.5 is public, same quality, better performance
• Impact: Users can now use embedding functionality out-of-the-box
• Compatibility: Existing users can still use --model jina-code if they have credentials

Critical Concerns

None identified. This is a proper release addressing a legitimate issue without compromising code quality or test integrity.

Final Recommendation

## Root Cause Analysis
**Problem Being Solved**: jina-code embedding model required HF_TOKEN authentication, causing crashes for unauthenticated users
**Why This Approach**: nomic-v1.5 is public, same dimensions, improved quality - fixes UX issue without breaking changes
**Risk Assessment**: LOW - Well-justified technical change with proper testing updates

## Critical Concerns
None - this addresses a real user-facing authentication issue

## Final Recommendation
- Rating: ⭐⭐⭐⭐☆ (4/5)  
- Action: **APPROVE**
- Reasoning: Clean release addressing legitimate authentication barrier. Proper test updates reflect intentional behavior change, not test weakening. No configuration relaxation or quality compromise detected.

---

[greptile-apps]

Greptile Summary

Automated release bumping version from 2.1.0 to 2.2.1, updating all platform-specific native dependency versions (@optave/codegraph-*) to match.

The DEPENDENCIES.json shows expected behavior - platform-specific packages that don't match the current CI environment (Linux x64) are flagged as "invalid", which is normal for optional dependencies that target other platforms.

Confidence Score: 5/5

• Safe to merge - automated version bump with consistent changes across all files
• This is a standard automated release process that correctly updates version numbers in package.json, package-lock.json, and DEPENDENCIES.json. All platform-specific optional dependencies are properly synchronized to 2.2.1. The "invalid" dependency entries in DEPENDENCIES.json reflect expected behavior for platform-specific packages on the CI runner.
• No files require special attention

Important Files Changed

Filename	Overview
package.json	Updated version from 2.1.0 to 2.2.1 and synced all platform-specific optional dependencies
package-lock.json	Lockfile updated to reflect version 2.2.1
DEPENDENCIES.json	Version bumped to 2.2.1, dependency tree regenerated showing platform-specific resolution differences

_{Last reviewed commit: 0ad955a}

[greptile-apps]

_{3 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}