chore: release v2.3.0

[carlos-alm]

Summary

Version bump to 2.3.0 with full changelog entry.

Highlights

• Graph-enriched embeddings — new structured strategy uses callers/callees from the dependency graph instead of raw source code (~100 tokens vs ~360 avg), with context window overflow detection
• Richer CLI — excludeTests config, --depth for explain, coupling scores in map, Mermaid output for diff-impact, --min-confidence filter for exports
• Robustness — graceful errors when no graph.db exists, concurrent file edit handling, symlink loop detection, Windows hook fixes
• Performance — reduced WASM boundary crossings in JS extractor
• /dogfood skill — automated release validation from Claude Code
• CI — query, incremental, and embedding regression benchmarks

Changes

• package.json → 2.3.0 (+ platform packages)
• package-lock.json → 2.3.0
• CHANGELOG.md → added v2.3.0 and missing v2.2.1 entries

Test plan

• Verify version numbers in package.json and package-lock.json
• Review CHANGELOG.md entries against commit history
• CI passes (lint, tests)

[claude]

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

---

PR Review Analysis

Conducting comprehensive review of release PR v2.3.0 following 4-phase analysis:

Todo List

• Phase 1: Root Cause Analysis - Determine what problem this PR solves
• Phase 2: Configuration Change Detection - Check for high-risk changes
• Phase 3: Test Integrity - Watch for red flags in tests
• Phase 4: Code Quality - Review implementation details
• Final Assessment - Provide rating and recommendation

Phase 1: Root Cause Analysis ✓

Problem Being Solved: This is a standard release preparation PR for version 2.3.0, bumping version numbers and updating changelog entries with features developed since v2.2.1.

Why This Approach: Uses conventional commit-and-tag-version release automation - only touches version metadata files (package.json, package-lock.json, CHANGELOG.md).

Phase 2: Configuration Change Detection ✓

No high-risk configuration changes detected:

• ✅ No linting rule modifications
• ✅ No test configuration changes
• ✅ No build configuration changes
• ✅ No TypeScript strict mode changes
• ✅ Only standard version bump files modified

Phase 3: Test Integrity ✓

No test integrity concerns:

• ✅ No test files modified
• ✅ No assertions weakened or removed
• ✅ No test timeouts increased
• ✅ No coverage thresholds lowered
• ✅ Automated release commit by github-actions[bot] - standard tooling

Phase 4: Code Quality ✓

Implementation Analysis:

• ✅ Version consistency: All platform package versions correctly updated from 2.2.1 → 2.3.0
• ✅ Changelog integrity: Referenced commit hashes exist (verified c5dcd59, 56135e7, 08057f0, 3f56644, dd71a64, 0fd1967)
• ✅ Release automation: Generated by commit-and-tag-version tooling with proper semantic versioning
• ✅ Feature documentation: Comprehensive changelog with proper categorization (Features, Bug Fixes, Performance, etc.)
• ✅ Minimal scope: Only metadata files changed, no code modifications

Root Cause Analysis

Problem Being Solved: Standard release process - consolidating features and fixes from 14+ commits into v2.3.0 release
Why This Approach: Automated tooling ensures consistency and prevents manual version sync errors
Risk Assessment: MINIMAL RISK - Pure metadata changes with no code modifications

Critical Concerns

None identified. This is a textbook example of a clean release PR.

Final Recommendation

• Rating: ⭐⭐⭐⭐☆ (4/5)
• Action: APPROVE
• Reasoning: This is a legitimate, well-structured release PR that follows established patterns. The changelog accurately reflects development work with verified commit references. Version numbers are consistent across all platform packages. No code changes or configuration relaxations present - only standard release metadata updates.

Minor consideration: The missing 5th star is due to inability to verify test suite passes, but the automated nature and scope limited to metadata files minimizes this concern.

---

[greptile-apps]

Greptile Summary

Version bump from 2.2.1 to 2.3.0 with comprehensive changelog documentation. The release includes graph-enriched embeddings, enhanced CLI features (excludeTests config, --depth for explain, coupling scores, Mermaid output), robustness improvements (graceful error handling, concurrent file edits, symlink loop detection), performance optimizations, and the new /dogfood skill for automated release validation.

All version numbers are consistent across package.json (main + 4 platform packages) and package-lock.json. The CHANGELOG entry properly documents the changes with commit references and also backfills the previously missing v2.2.1 entry.

Confidence Score: 5/5

• Safe to merge - standard release version bump with no code changes
• This is a clean release PR that only updates version numbers and documentation. All version numbers are consistent across package.json and package-lock.json (main package: 2.3.0, all 4 platform packages: 2.3.0). The CHANGELOG.md accurately documents features and fixes with proper commit references verified against git history. No functional code changes means zero risk of introducing bugs.
• No files require special attention

Important Files Changed

Filename	Overview
package.json	Version bumped from 2.2.1 to 2.3.0 for main package and all platform-specific optional dependencies
package-lock.json	Lockfile version updated to match package.json 2.3.0 changes across all entries
CHANGELOG.md	Added v2.3.0 entry with comprehensive feature list, bug fixes, and performance improvements; also backfilled missing v2.2.1 entry

_{Last reviewed commit: 68c2139}

[greptile-apps]

_{3 files reviewed, no comments}

_{Edit Code Review Agent Settings | Greptile}