v0.3.2 — PR indexing actually works
PR indexing works for the first time
PR_QUERY asked GitHub for diffHunk on PullRequestReviewThread, a field GitHub defines only on PullRequestReviewComment. GitHub rejected the entire query with undefinedField, so every fetch failed before a single PR was indexed.
If you are on 0.3.0 or 0.3.1, you cannot index any repository. Upgrade.
Verified against the live API: 93 of 95 review comments in a 300-PR langchain-ai/langchain fetch now carry a diff hunk, where the request previously returned nothing at all. tests/test_queries_schema.py guards the field's placement so the query cannot silently drift from GitHub's schema again.
First release carrying the v3 work
v0.3.1 was tagged before the hardening branch merged, so none of this has ever appeared in a published artifact:
- GitHub App Device Flow with OS-vault-only credentials — no personal access tokens
- Retrieval-only boundary: the server returns evidence, the IDE agent reasons
- Namespace-scoped storage and
migrate-storage - Async index jobs, durable capped-refresh continuation
- Incremental indexing by webhook
- Comment-quality filtering
Breaking change
Numbered as a patch, but Device Flow replaces personal access tokens. Upgrading from 0.3.0 or 0.3.1 means reconnecting GitHub and running migrate-storage.
Also in this release
- Webhook indexing no longer advances the refresh watermark, which had let later refreshes skip PRs updated earlier but not yet indexed
- Review-summary bot metadata no longer leaks the previous loop's inline-comment flag
- PR replay benchmark scoring against real merged diffs. It reports no statistically demonstrated effect — the measured gap is smaller than the judge's own scatter. See
benchmarks/README.md - Diagram-first README
uvx github-pr-context-mcpFull changelog: https://github.com/paarths-collab/github-pr-context-mcp/blob/main/CHANGELOG.md