chore: release v3.1.0

[carlos-alm]

Summary

• Bump version to 3.1.0 across package.json, package-lock.json, and Cargo.toml
• Add CHANGELOG entry for 3.1.0: sequence command, --unused exports flag, 6 native engine perf optimizations, ~80x no-op rebuild regression fix, dependency bumps
• Fix README wording ("half its token budget" → "a great portion of its token budget")

Test plan

• Verify npm run release:dry-run detects no further changes
• Confirm CI passes on all platforms
• Trigger publish workflow with version 3.1.0 after merge

[claude]

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

---

Reviewing PR #364: chore: release v3.1.0

Review Checklist:

• Phase 1: Root Cause Analysis - Understand what problem this PR solves
• Phase 2: Configuration Change Detection - Check for high-risk changes
• Phase 3: Test Integrity - Look for test weakening or removed assertions
• Phase 4: Code Quality - Review implementation details
• Final Assessment - Provide rating and recommendation

Root Cause Analysis

Problem Being Solved: This is a standard release preparation PR to bump the project from v3.0.4 to v3.1.0. Based on the extensive changelog, this release includes significant new features (sequence command, unused export detection) and performance improvements (native engine optimizations, ~80x no-op rebuild fix).

Why This Approach: Standard semantic versioning release process using commit-and-tag-version - legitimate minor version bump for new features. Version consistency maintained across package.json, package-lock.json, and Cargo.toml.

Risk Assessment: LOW RISK - This is a legitimate release PR with no configuration relaxations, test weakening, or suspicious changes.

Configuration Change Detection ✅

NO HIGH-RISK CHANGES DETECTED:

• ✅ No biome/linting rules modified
• ✅ No test timeouts or coverage thresholds changed
• ✅ No build configuration modifications
• ✅ No TypeScript strict mode changes
• ✅ Version bumps are consistent across all files

Test Integrity ✅

NO RED FLAGS:

• ✅ No test files modified
• ✅ No assertions removed or weakened
• ✅ No eslint-disable comments added
• ✅ Small, focused PR (5 files changed)
• ✅ Single logical concern (release preparation)

Code Quality Review ✅

Version Consistency: ✅ All version references properly updated:

• package.json: 3.0.4 → 3.1.0 ✅
• package-lock.json: 3.0.4 → 3.1.0 ✅
• Cargo.toml: 3.0.4 → 3.1.0 ✅

CHANGELOG.md: ✅ Comprehensive and well-structured:

• Proper semantic versioning categorization (Features, Performance, Bug Fixes)
• Detailed descriptions with PR references
• No suspicious or concerning entries
• Legitimate performance improvements and bug fixes documented

README.md: ✅ Minor wording improvement:

• "half its token budget" → "a great portion of its token budget"
• Sensible change that avoids specific quantification

Final Assessment

## Root Cause Analysis
**Problem Being Solved**: Standard v3.1.0 release preparation with legitimate feature additions and performance improvements
**Why This Approach**: Proper semantic versioning workflow using commit-and-tag-version 
**Risk Assessment**: LOW - No configuration relaxations or suspicious changes

## Critical Concerns
None identified. This is a well-executed release PR.

## Final Recommendation  
- Rating: ⭐⭐⭐⭐☆ (4/5)
- Action: APPROVE
- Reasoning: Clean release PR with proper version consistency, comprehensive changelog, and no concerning changes. Standard release workflow execution.

This is a textbook example of a proper release PR. All version numbers are consistent, the changelog is comprehensive and legitimate, and there are no configuration relaxations or test weakening patterns.

[greptile-apps]

Greptile Summary

This is a clean release PR that bumps @optave/codegraph from v3.0.4 to v3.1.0 across all version files (package.json, package-lock.json, crates/codegraph-core/Cargo.toml), adds the corresponding CHANGELOG.md entry, and corrects a minor README claim.

• Version 3.1.0 is applied consistently in all three version-bearing files — no mismatches found.
• The CHANGELOG entry is well-structured and consistent with previous entries, accurately documenting the new sequence command, --unused exports flag, six native engine performance optimisations, the ~80x no-op rebuild regression fix, and dependency bumps.
• The README wording change ("half its token budget" → "a great portion of its token budget") is a minor but accurate improvement.
• No logic, syntax, or security issues were identified in the changeset.

Confidence Score: 5/5

• This PR is safe to merge — it contains only version bumps, a CHANGELOG entry, and a one-line README wording fix with no functional code changes.
• All changes are mechanical release artifacts: three version fields bumped identically, a CHANGELOG section that mirrors the commit history, and a minor prose correction. There is no logic, no new code paths, and no risk of regression.
• No files require special attention.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A([PR: chore/release v3.1.0]) --> B[Version bump 3.0.4 → 3.1.0]
    B --> C[package.json]
    B --> D[package-lock.json]
    B --> E[crates/codegraph-core/Cargo.toml]
    A --> F[CHANGELOG.md — add v3.1.0 entry]
    F --> G[Features: sequence command, --unused flag]
    F --> H[Performance: 6 native engine optimisations]
    F --> I[Bug Fixes: ~80x no-op rebuild regression]
    F --> J[Chores: dep bumps]
    A --> K[README.md — minor wording fix]

Loading

_{Last reviewed commit: 290ed57}