chore(release): prepare 0.6.5#254
Conversation
Cut the 0.6.5 release and bump every user-facing version reference ahead of tagging. Since 0.6.4 the engine gained three changes, all already merged and CI-green on main: - #251 (feat) — default `dikw init` scaffold now ships a Gitee `bge-m3` embedder + `bge-reranker-v2-m3` reranker keyed by one `GITEE_API_KEY`, and rerank/embed degrade-logging is unified (transient leg failures log at ERROR, enabled-but-unconfigured / deferred-embed log at WARNING; permanent provider errors still fail fast). - #250 (fix) — eval snapshot cache key now includes the ingest-time `cjk_tokenizer` and reads every search-time retrieval knob from the live config, so retrieval ablations on a shared `cache_root` under the default `--cache read_write` stop silently reusing the prior run's config. - #249 (feat) — eval per-query + negative rows surface `top1_score` and `top1_vec_cosine` (reranker-independent, via an eval-internal probe) so expect_none / OOD robustness is measurable from absolute relevance. Mechanics (mirrors the prepare-0.6.4 PR #247): - Version bump `0.6.4 -> 0.6.5` (`pyproject.toml` + `uv.lock` self-entry). - CHANGELOG: rename `## Unreleased` -> `## 0.6.5 — …` (Added/Changed/Fixed), open a fresh empty `## Unreleased`. The 0.6.5 heading is awk-extractable by `release.yml`'s notes extractor. - Docs/examples: bump the GHCR image tags (`docs/deployment-docker.md`), the pip-install pin (`docs/getting-started.md`), the compose `.env` default + error-message example (`examples/docker/.env.example`, `docker-compose.yml`), and the bug-report version placeholder. - `examples/docker/Dockerfile` intentionally NOT bumped — `release.yml`'s `sync-dockerfile` job auto-bumps it after the tag publishes to PyPI; its current 0.6.4 is published, so the Dockerfile guard stays green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 12 minutes and 3 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
1 participant
Cut 0.6.5 and bump every user-facing version reference ahead of tagging. Mirrors the prepare-0.6.4 PR (#247).
What's in 0.6.5 (all already merged + CI-green on main)
dikw initscaffold ships Giteebge-m3embed +bge-reranker-v2-m3rerank (oneGITEE_API_KEY); unified rerank/embed degrade-logging (transient→ERROR, deferred/unconfigured→WARNING; permanent provider errors still fail fast).cjk_tokenizerand reads search-time retrieval config live — retrieval ablations on a sharedcache_rootunder--cache read_writestop silently reusing the prior config.top1_scoreandtop1_vec_cosine(reranker-independent, eval-internal probe) for expect_none / OOD calibration.Mechanics
0.6.4 → 0.6.5(pyproject.toml+uv.lockself-entry).## Unreleased→## 0.6.5 — …(Added/Changed/Fixed), fresh empty## Unreleased. Heading is awk-extractable byrelease.yml..envdefault + error-message example, bug-report placeholder.examples/docker/Dockerfileintentionally not bumped —release.yml'ssync-dockerfileauto-bumps it after the tag publishes to PyPI; its current0.6.4is published so the Dockerfile guard stays green.Verification
tools/check.py(ruff + mypy + fast pytest) — green (2409 passed).tools/check_doc_refs.py— green.src/change → eval-gate does not fire (no baseline needed).🤖 Generated with Claude Code