release: v0.32.0 — full-codebase retrieval coverage, answer-quality fixes, new stats signals#854
Merged
Conversation
|
✅ Health: 7.6 (unchanged) 📋 At a glance 🩹 Review priority (files here with the most recent bug-fix history — defects cluster, so review these first)
🔎 More signals (2)🔥 Hotspots touched (3)
🔗 Hidden coupling (3 files)
📊 Full report · ⭐ Star Repowise · 📥 Install bot · Last updated 2026-07-15 16:04 UTC |
RaghavChamadiya
approved these changes
Jul 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts v0.32.0 from
main(20 commits since v0.31.0). Bump + changelog only — no functional changes in this branch.What's in the release
The theme this cycle is retrieval coverage: every parsed file now gets a page (deterministic tail, #817/#819), so concept search reaches the whole codebase rather than the ~20% the LLM budget covers. Alongside that, a batch of
get_answer/ search-quality fixes, new stats signals, a Kimi provider, and decisions delivered into Codex.Full breakdown in
docs/CHANGELOG.md.Version bump
Six synchronized files + lockfile:
pyproject.toml,packages/{cli,core,server}/src/**/__init__.py→0.32.0.claude-plugin/marketplace.json,plugins/claude-code/.claude-plugin/plugin.json→0.32.0uv.lockself-entry0.31.0 → 0.32.0(via explicituv lock)Not bumped, deliberately:
STORE_FORMAT_VERSION/PARSER_SCHEMA_VERSIONstay at1. The Go change (fix(go): detect function references in go to rescue FPs on dead-code #815) is a.scmquery — its bytes are already hashed into the parse-cache fingerprint. The with-statement fix (fix(dataflow): recurse into with-statement bodies #836) is inanalysis/health/dataflow, not the ingestion parser that producesParsedFile. No store reacts, no cache churn.plugins/codex/.codex-plugin/plugin.jsonstays at0.1.1—plugins/codex/has no diff since v0.31.0. (feat(codex): deliver architectural decisions into Codex SessionStart #788 landed in the CLI hook code, not the plugin dir.)packages/vscode/package.json— rides its own version line; no extension release in this window.Test plan
uv lock— self-entry moved; drift grep clean (remaining0.31.0hits are the coincidentalasyncpgdep)uv build --wheel→dist/repowise-0.32.0-py3-none-any.whl, 69 command modules incl.serve_cmd.py, 38.scm/.j2data files, bundled changelog presentnpm ci && npm run build --workspace packages/web— green, all routes built, standaloneserver.jsemitted, workspace-package code transpiled into chunks. Middleware entry (34.3 kB) present, confirming Fix #838: Use Next.js Middleware for dynamic proxying of API routes #839 compiledtests/unit/upgrade/test_bundled_changelog_sync.pypasseslist_tools()set.get_architecture_diagramappears only in the plugin CHANGELOG documenting its removal, which is expectedv0.32.0on the squash commit, push tag →publish.yml