docs: update 2.6.0 changelog with dogfood bug fixes#242
Conversation
…ld docs - Add node/edge count drift detection after incremental builds (>20% warns to use --no-incremental), persisting counts in build_meta - Improve complexity command: when data is missing but graph exists, suggest --no-incremental instead of implying no graph exists - Add @huggingface/transformers as devDependency so embedding benchmarks work out of the box - Document dev build tarball installation in README (npm install <url> fails for optional platform deps) Impact: 3 functions changed, 5 affected
…provements Impact: 1 functions changed, 1 affected
- Add build.driftThreshold to config defaults (0.2) so the 20% incremental build drift threshold is user-configurable - Include actual drift percentages and threshold in warning message for easier debugging - Regenerate package-lock.json to include @huggingface/transformers devDependency (fixes License Compliance Scan CI failure) Impact: 1 functions changed, 1 affected
…ative version - filter directory nodes from reverse-deps query to prevent EISDIR (#235) - load unchanged barrel files into reexportMap so barrel-resolved edges aren't dropped during incremental rebuilds (#236) - add --strip flag to sync-native-versions.js removing platform optionalDependencies in dev builds, fixing npm install failures (#237) - sync Cargo.toml version with package.json and automate via version script - add barrel-project fixture and incremental-parity test Impact: 4 functions changed, 1 affected
|
Claude finished @carlos-alm's task —— View job PR Review: docs: update 2.6.0 changelog with dogfood bug fixesTodo List:
Root Cause AnalysisProblem Being Solved: Updating 2.6.0 changelog to document bug fixes from PRs #233, #239, #240, #241 that were merged after initial changelog was written. These fixes address incremental build reliability issues. Why This Approach: Legitimate documentation update for existing merged fixes. The actual bug fixes are already in the codebase - this PR just documents them properly in the changelog. Risk Assessment: Low risk - primarily documentation changes with supporting test infrastructure. Critical ConcernsNone detected. This is a well-structured documentation update. Code Quality Assessment ✅Documentation Quality:
Supporting Code Changes (from previous commits):
Test Quality:
Script Changes:
Final Recommendation
Minor Positives:
No concerns identified - this is exactly how changelog updates should be done after merging related bug fixes. |
Greptile SummaryThis PR updates the 2.6.0 CHANGELOG with bug fix entries from previously merged PRs #233, #239, #240, and #241. The actual code changes shown in the diff are from those prior PRs and were already merged to main. What changed:
Important context: The changelog entries accurately describe the changes from the referenced PRs and follow the project's conventional commit format. Confidence Score: 5/5
Important Files Changed
Last reviewed commit: dd9b510 |
Summary